Aircraft Accident/Incident Report

Bradenton, Florida 34202
Thursday, November 16, 2000 15:48 EST

NTSB Narrative Summary Released at Completion of Accident

A formation flight of two F-16s departed Moody Air Force Base in Valdosta, Georgia, on an IFR flight plan leading to the entry point for a low-altitude military training route located near Sarasota, Florida. The flight lead pilot was provided an air traffic control (ATC) frequency change from Miami Center to Tampa Approach. The flight was unable to establish communications with Tampa Approach because an incorrect radio frequency was given to the flight lead by Miami Center. The flight lead reestablished radio contact with Miami Center, cancelled the flight's IFR clearance, and proceeded under visual flight rules (VFR). The controller acknowledged the cancellation, advised the F-16 flight lead pilot of traffic in his vicinity, and asked the flight lead pilot if he wanted VFR flight following (a service that includes VFR radar traffic advisories on a workload-permitting basis.). The flight lead pilot declined. The Miami Center controller then informed Tampa Approach that the flight lead pilot had elected to terminate ATC services, but did not specify that there were two aircraft in the flight. Tampa Approach procedures did not require that the controllers use flight strips (which would have included the number of aircraft in the formation), so the Tampa controllers had no other information indicating that there were multiple aircraft present. Continuing their descent under VFR, the two F-16s assumed the “fighting wing” formation. This placed the accident F-16 on the left side of the lead aircraft and approximately 0.7 miles in trail. The accident F-16’s transponder was inactive, as is normal for formation operations, making the aircraft significantly less conspicuous on ATC radar than it would be with an operating transponder. At an unknown point in the flight, the F-16 lead pilot’s navigation system developed a position error and was indicating that the aircraft was several miles from its actual position. The pilot failed to recognize the error, and was attempting to visually locate the entry point for the training route based on the erroneous navigation data. Because of the lead pilot’s loss of situational awareness, the two F-16s inadvertently descended into the Class C airspace surrounding the Sarasota, Florida airport without establishing required communications with ATC. Meanwhile, a Cessna 172 pilot departed Sarasota under VFR and contacted Tampa Approach. The Cessna pilot was instructed by the developmental controller receiving instruction to maintain 1,600 feet, turn left to a heading of 320-degrees, and to follow the shoreline. At 15:47:10, he was instructed to climb and maintain 3,500 feet. Miami Center contacted Tampa Approach at 15:47:55, and asked for the altitude of the F-16s. Although the Tampa controller was not in contact with the F-16s, he was able to locate the flight lead on the radar display and informed Miami that the flight lead was at 2,000 feet. A conflict alert between the lead F-16 and the Cessna activated 10 times between 15:47:39 and 15:48:03. The developmental controller stated that he heard an alarm, but could not recall where it was. The controller providing the instruction did not recall if he saw or heard a conflict alert, and no conflict alert was issued. There was no alert generated between the accident F-16 and the Cessna because the conflict alert system requires that both aircraft involved have operating transponders. The developmental controller informed the Cessna pilot at 15:48:09 that he had traffic off his left side, but received no response. The controllers were unaware of the position of the other (accident) F-16 in the formation flight. At 15:48:53, the lead F-16 transmitted, “Mayday, mayday.” At 15:49:14, the flight lead pilot followed with, "Mayday, mayday, mayday, F-16 down." Examination of the wreckage of both airplanes determined that the accident F-16's left wing and cockpit area collided with the Cessna 172's right forward side (nose) and cabin area.

NTSB Probable Cause Narrative

the failure of the F-16 flight lead pilot and F-16 accident pilot to maintain an adequate visual lookout while maneuvering. Factors contributing to the accident were: the F-16 flight lead pilot’s decision to discontinue radar traffic advisory service, the F-16 flight lead pilot’s failure to identify a position error in his aircraft’s navigational system, the F-16 pilots subsequent inadvertent entry into class C airspace without establishing and maintaining required communications with air traffic control (ATC); and ATC’s lack of awareness that there was more than one F-16 aircraft in the formation flight, which reduced the ATC controllers ability to detect and resolve the conflict that resulted in the collision.

Event Information

Type of Event Accident
Event Date 11/16/2000
Event Day of the Week Thursday
Time of Event 1548
Event Time Zone Eastern Standard Time
Event City BRADENTON
Event State FLORIDA
Event Country --
Zipcode of the event site 34202
Event Date Year 2000
Event Date Month 11
MidAir Collision Indicator Yes
On Ground Collision occurred ? No
Event Location Latitude 272606N
Event Location Longitude 0822700W
Event Location Airport --
Event Location Nearest Airport ID --
Indicates whether the acc/inc occurred off or on an airport Off Airport/Airstrip
Distance from airport in statute miles --
Degrees magnetic from airport --
Airport Elevation --
Weather Briefing Completeness Unknown
Investigator's weather source Weather Observation Facility
Time of the weather observation 1553 Eastern Standard Time
Direction of event from weather observation facility (degrees) 274
Weather Observation Facility ID SRQ
Elevation of weather observation facility 27
Distance of event from weather observation facility (units?) 5
Time Zone of the weather observation EST
Lighting Conditions Day
Lowest Ceiling Height --
Lowest Non-Ceiling Height --
Sky/Lowest/Cloud Conditions Clear
Sky Condition for Lowest Ceiling None
Visibility Runway Visual Range (Feet) 0
Visibility Runway Visual Value (Statute Miles) 0
Visibility (Statute Miles) 10
Air Temperature at event time (in degrees celsius) 27
Dew Point at event time (in degress fahrenheit) 18
Wind Direction (degrees magnetic) 210
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) 11
Wind Velocity Indicator --
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 29
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report --
Event Highest Injury Fatal
On Ground, Fatal Injuries 0
On Ground, Minor Injuries 0
On Ground, Serious Injuries 0
Injury Total Fatal 1
Injury Total Minor --
Injury Total None 1
Injury Total Serious --
Injury Total All 1
Investigating Agency NTSB
NTSB Docket Number (internal use) 11754
NTSB Notification Source FAA COMM CNTR ATL
NTSB Notification Date Nov 16 2000 12:00AM
NTSB Notification Time 1630
Fiche Number and/or location -used to find docket information DMS
Date of most recent change to record Jan 23 2003 4:18PM
User who most recently changed record NTSB\JOHB
Basic weather conditions Visual Meteorological Cond
FAA District Office --

Aircraft Involved

Aircraft #1

Aircraft #2

Aircraft Registration Number USAF N73829
NTSB Number MIA01FA028A MIA01FA028B
Missing Aircraft Indicator N N
Federal Aviation Reg. Part Part 91: General Aviation Part 91: General Aviation
Type of Flight Plan filed VFR/IFR None
Flight plan Was Activated? Yes No
Damage Destroyed Destroyed
Aircraft Fire Ground None
Aircraft Explosion Ground None
Aircraft Manufacturer's Full Name Lockheed-Martin Cessna
Aircraft Model F-16CG 172N
Aircraft Series Identifier F-16CG 172N
Aircraft Serial Number 89-2104 17267705
Certified Max Gross Weight 42300 2300
Aircraft Category Airplane Airplane
Aircraft Registration Class Military U.S. Registered/U.S. Soil
Aircraft is a homebuilt? No No
Flight Crew Seats -- --
Cabin Crew Seats -- --
Passenger Seats -- --
Total number of seats on the aircraft 1 4
Number of Engines 1 1
Fixed gear or retractable gear Retractable Fixed
Aircraft, Type of Last Inspection Continuous Airworthiness 100 Hour
Date of Last Inspection Sep 21 2000 12:00AM Nov 13 2000 12:00AM
Airframe hours since last inspection 640 7
Airframe Hours 3244 5631
ELT Installed No Yes
ELT Activated Unknown Unknown
ELT Aided Location of Event Site No No
ELT Type -- --
Aircraft Owner Name HQ Air Combat Command CRYSTAL AERO GROUP INC
Aircraft Owner Street Address 205 Dodd Blvd Suite 100 PO BOX 2050
Aircraft Owner City Langely A.F. B. CRYSTAL RIVER
Aircraft Owner State VA FL
Aircraft Owner Country USA --
Aircraft Owner Zipcode 23665 34423
Operator is an individual? No No
Operator Name 69TH FIGHTER SQD, 347TH WING --
Operator Same as Owner? No Yes
Operator Is Doing Business As -- --
Operator Address Same as Owner? No Yes
Operator Street Address 8223 KNIGHT WAY --
Operator City VALDOSTA --
Operator State GA --
Operator Country -- --
Operator Zip code 31699 --
Operator Code -- --
Owner has at least one certificate None None
Other Operator of large aircraft? -- --
Certified for Part 133 or 137 Operation -- --
Operator Certificate Number -- --
Indicates whether an air carrier operation was scheduled or not -- --
Indicates Domestic or International Flight -- --
Operator carrying Pax/Cargo/Mail -- --
Type of Flying (Per_Bus / Primary) Instructional Personal
Second Pilot on Board No No
Departure Point Same as Event No No
Departure Airport Code VAD SRQ
Departure City VALDOSTA SARASOTA
Departure State GA FL
Departure Country USA USA
Departure Time 1513 1541
Departure Time Zone EST EST
Destination Same as Local Flt dest & departure same, accident can occur anywhere --
Destination Airport Code VAD SPG
Destination City -- ST. PETERSBURG
Destination State GA FL
Destination Country -- --
Specific Phase of Flight Maneuvering Maneuvering
Report sent to ICAO? -- --
Evacuation occurred Yes No
Date of most recent change to record Sep 30 2004 12:48PM May 8 2002 10:48AM
User who most recently changed record NTSB\HAMG KENJ
Since inspection or accident Time of Accident Time of Accident
Event Location Runway Number and Location 0 0
Runway Length -- --
Runway Width -- --
Sight Seeing flight No No
Air Medical Flight No No
Medical Flight -- --