F-16 Aircraft Database

Airframe Details for F-16 #88-0404




F-16 Aircraft Profile

Aircraft: : 88-0404
LM Aero T/V 5C-618
Plant General Dynamics
Local C/N
Delivered USAF 88404
F-16C Block 30K
Current USAF 88404
F-16C Block 30K
Status [act]

⇦ Copy-paste this code to link this airframe from our forum

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
31 Jul 1989 [act] 88404 F-16C Block 30K
Aug 1989 [act] 88404 USAF 26 AS F-16C Block 30K
Was to be assigned to the 26th AS and was painted in the Flanker paint scheme and was diverted to the 35th TFS.
Sep 1989 [act] 88404 USAF 35 TFS 'WP' F-16C Block 30K
01 Oct 1991 [act] 88404 USAF 35 FS 'WP' F-16C Block 30K
Unknown [act] 88404 USAF 35 FS 'WP' F-16C Block 30K
Special characteristics:
  • Unit Markings: 8 FW
May 2001 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Oct 2001 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Deployment: Enduring Freedom

Unknown [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Jan 2003 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Deployment: Southern Watch

Feb 2003 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Special characteristics:
  • Mission Marks
  • Unit Markings: 482 FW
Shortly after returning from last deployment, tail text of the 482nd FW boss bird markings were added. By the end of the year, mission markings were added on the right side of aircraft just aft of the canopy showing 26 bombs dropped during Operation Enduring Freedom in 2001 and 48 bombs dropped in Operation Southern Watch during build up for Iraqi Freedom which started on March 20, 2003.
Sep 2005 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Deployment: Iraqi Freedom

Unknown [msh] 88404 USAF 93 FS 'FM' F-16C Block 30K
Ran off the runway at Balad AB.
Unknown [sto] 88404 USAF OO-ALC F-16C Block 30K
Under repair at Ogden ALC, Utah. It is thought the aircraft returned to service and was broken again for up to six months, but unrelated to the first mishap.
Oct 2007 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Oct 2016 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Special characteristics:
  • Unit Markings: 482 FW
Special 'Shark' scheme applied.
Nov 2018 [act] 88404 USAF 93 FS 'FM' F-16C Block 30K
Special characteristics:
  • Unit Markings: 482 FW

Crew Chief Comments

Create your own Crew Chief Profile
If you crewed this jet and want to leave a comment, you can create your own profile in our Crew Chief Profiles section.

SMSgt. Sean Bailey

Crew Chief Profile
93rd Fighter Squadron "Makos" , -


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



Any aircraft or serials missing from this list? Did you see incorrect, incomplete, or outdated data?
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]


Errors and Omissions

Nov 02, 2006 - 08:25 PM
Confusing dates?

Above, the mishap is dated 09 oct 2005. But also in oct 2005 there is a photo on October 18th, 2005. [USAF photo by TSgt. Paul Dean]. I don't think this can both be right as the damage on 09 oct 2005 exceeded 1 million dollars, as stated. So my question is: which date(s) is/are correct?

Jon
Nov 02, 2006 - 08:33 PM
Yes - confusing dates

This confusion of dates is most likely the error on the USAF photo. I have spent many hours searching the DVIC web site for USAF photos and it is amazing how many have incorrect dates or other information. Had not noticed this mistake before, so good eye :-)

It is most likely that the photo was taken within a couple weeks of the mishap.




Note: Errors and omissions in the above text can be added here. Please 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.