F-16 Aircraft Database
Airframe Details for F-16 #80-0627
F-16 Aircraft Profile
Aircraft:
80-0627
|
||
LM Aero T/V | 62-69 | |
Plant | General Dynamics | |
Local C/N | ||
Delivered |
USAF
80627
F-16B Block 10C |
|
Current |
USAF
80627
F-16B Block 10C |
|
Status | [w/o] | |
|
⇦ Copy-paste this code to link this airframe from our forum
Aircraft History
Date | Status | Local S/N | Airforce/Unit | Version | Name | Info | ||
---|---|---|---|---|---|---|---|---|
31 Aug 1981 | [act] | 80627 | F-16B Block 10C | |||||
Sep 1981 | [act] | 80627 | USAF 63 TFTS 'MC' | F-16B Block 10C | ||||
11 Jul 1983 | [msh] | 80627 | USAF 63 TFTS 'MC' | F-16B Block 10C | ||||
|
||||||||
11 Jul 1983 | [w/o] | 80627 | USAF 63 TFTS 'MC' | F-16B Block 10C |
Crew Chief Comments
Create your own Crew Chief ProfileIf you crewed this jet and want to leave a comment, you can create your own profile in our Crew Chief Profiles section.
Abbreviations and symbols:
[act] | Active | [i/a] | Instructional Airframe | [sto] | Stored (e.g. at AMARG) |
[cld] | Cancelled Order | [msh] | Involved in Mishap | [w/o] | Write-off |
[con] | Converted | [o/o] | On Order | ||
[des] | Destroyed (drone) | [pre] | Preserved (museum, gateguard) | T/V | LM Aero Type/Version (Construction) number |
[emb] | Embargoed | [scr] | Scrapped | Photo Available |
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]
It was never determined exactly what stage the engine fuel control was in, Maintenance personnel routinely advanced the engine fuel control to approximately the military power setting when connecting the linkage, which was in violation of standard procedures for engine installation. Only the nose landing gear collapsed when the aircraft left the paved apron and impacted the ditch immediately adjacent to the apron. There was no 25 yard hole in the ground. When the nose gear failed the aircraft struck the ground, causing the engine to break in half at the fan/compressor sections. Blades from the engine penetrated the fuel cell above the engine causing leaks and a fire. The fire plume came from the engine intake and impinged the cockpit and canopy. The person in the aircraft performing the engine run successfully raised the canopy and jumped over the side of the aircraft without injury. As was standard procedures for ground engine runs a fire suppression vehicle was present and immediately doused the fire.
The aircraft was subsequently sent to Hill AFB Air Logistics Center for repair. A complete nose section was re-purchased from the Israeli Air Force and installed on the aircraft.
Both personnel who performed the final steps of the engine installation were later convicted of falsifying military records for their documentation on the aircraft. The seven-level technician cleared all the Red X AFTO Form 781 entries in the "inspected by" block when he had no done so, the five-level technician signed all the "corrected by" blocks in the 781s. What really occurred was the five-level went down the right side of the engine (which included the throttle linkage) and the seven-level went down the left side of the engine and made all the necessary connections after the engine had been "five-pointed" the previous evening. They got together and signed off (incorrectly) all of the engine installation entries in the AFTO 781s.
This aircraft image and tail number is incorrect. The aircraft in this incident was an A model, single seat. I have not yet been able to confirm the tail number. I have a picture of the crashed aircraft where it landed in the grass. I was an instructor at MacDill when the described accident happened. I also have not been able to to confirm the date. On the date stated here, A B model F-16, 80-627 crashed in the gulf of Mexico, it was a B model aircraft. I have the image and description from the Tampa Tribune.
Please use this form to add any list any error or omissions you find in the above text.
Note: your comments will be displayed immediately on this page. If you wish to send a private comment to the webmasters, please use the Contact Us link.