MIA01FA028 · Lockheed-Martin F-16CG
Lockheed-Martin F-16CG and Cessna 172N · Accident: midair collision while maneuvering
Event
- NTSB case
- MIA01FA028
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Lockheed-Martin F-16CG
- Aircraft type
- Lockheed Martin F-16
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- USAF
- Operator
- 69TH Fighter SQD, 347TH Wing
- Onboard fatalities
- Unknown
- Route
- From Moody Air Force Base (VAD), Valdosta, GATo Moody Air Force Base (VAD), GA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Cessna 172N
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N73829
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sarasota Bradenton International Airport (SRQ), Sarasota, FLTo Albert Whitted Airport (SPG), St. Petersburg, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Atc personnel(dep/apch) › Artcc service, not issued
- Pilot in command › Visual lookout, not maintained
- Pilot of other aircraft › Communications/information/atc, discontinued
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01FA028
- Event ID
- 20001212X22313
- Case number
- MIA01FA028
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d6381a963668b207d4643cab1b6a368efeb6afe8154013336afce7c8f8576c64; retrieved 2026-09-20T20:47:12.344Z.