F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #92-3889

[Back to F-16 Aircraft Database menu | Missing Photos | Hall of Fame]



F-16 Aircraft Profile

Aircraft: 92-3889
LM Aero T/V CC-131
Plant Lockheed - Fort Worth
Local C/N
Delivered USAF 92889
F-16C Block 52P
Current USAF 92889
F-16C Block 52P
Status [act]
Possible mishap involving this aircraft with the 389th FS. Throttle stuck on landing, pilot held the brakes till end of runway at Nellis AFB during a Red Flag exercise. The left main gear caught fire. Fire was quickly extinguished and parts replaced as a class B mishap. Exact date and confirmation of serial is yet to be made with this mishap.


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

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
24 May 1994 [act] 92889 F-16C Block 52P
02 Jun 1994 [act] 92889 USAF 389 FS 'MO' F-16C Block 52P
Apr 1998 [act] 92889 USAF 389 FS 'MO' F-16C Block 52P
Deployment: Southern Watch

Unknown [act] 92889 USAF 389 FS 'MO' F-16C Block 52P
Nov 2001 [act] 92889 USAF 389 FS 'MO' F-16C Block 52P " Vulture, T-bolts rule"
Special characteristics:
  • Nose Art
  • Mission Marks
Deployment: Enduring Freedom

12 mission markings for Operation Enduring Freedom. Art work by TSgt Robbie Leist and SSgt Chad Marks.
Unknown [act] 92889 USAF 389 FS 'MO' F-16C Block 52P
Aug 2004 [msh] 92889 USAF 389 FS 'MO' F-16C Block 52P AIB Report
Returned from a training flight code one in Japan during a TDY. Taxiing back to it's parking spot the aircraft hit a pot hole causing a short in the ECM pod adapter. That resulted in sparks starting a fire. The aircraft was taken apart and shipped back in March 2005 to Mountain Home AFB and repaired by a team from Hill AFB. By July 2005 the aircraft was finally repaired and after a few test flights and scheduled upgrades was back in service. Mishap was graded a class A but was later downgraded to a class B. The aircraft was flown back to the United States aboard a C-5.
Jul 2005 [act] 92889 USAF 389 FS 'MO' F-16C Block 52P
29 Mar 2007 [act] 92889 USAF 157 FS F-16C Block 52P
12 Apr 2012 [act] 92889 USAF 157 FS F-16C Block 52P
Deployment: Enduring Freedom

23 Aug 2012 [act] 92889 USAF 157 FS F-16C Block 52P
Nov 2014 [act] 92889 USAF 157 FS F-16C Block 52P
Special characteristics:
  • Mission Marks

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.

SSgt. Austin Harding

Crew Chief Profile
389th Fighter Squadron "Thunderbolts" , 2004 - 2005
My first jet, basically I was on it for a total of 8 months.

SSgt. Chip Rutland

Crew Chief Profile
389th Fighter Squadron "Thunderbolts" , 1998 - 1999
This was my first Jet. It was not the Flagship, However, everytime the Colonel flew, he flew this jet.

MSgt. Donald DePedro

Crew Chief Profile
389th Fighter Squadron "Thunderbolts" , 1995 - 1997
The war machine. This aircraft always deployed, even when it was a spare. It was a flying machine.

MSgt. Donald DePedro

Crew Chief Profile
389th Fighter Squadron "Thunderbolts" , 1998 - 2006
Back from the Kun and got my aircraft back. The war machine! Had to leave her in 2001 when I went to QA. Came back as an expediter in 2002 and watched over her again. Now they are going to the Guard and I had to leave the F-16 community.


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




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.