Printed from: F-16.net - The Ultimate F-16 Reference [http://www.f-16.net] Document title: F-16.net - The Ultimate F-16 Reference Original URL: http://www.f-16.net/f-16_fighting_falcon_airframe-3782.html Printed on: 12 October 2008
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 the F-16.net forum
Aircraft History
Date
Status
Local S/N
Airforce/Unit
Version
Name
Info
24 May 1994
[act]
92889
F-16C Block 52P
Jun 1994
[act]
92889
389 FS 'MO'
F-16C Block 52P
Apr 1998
[act]
92889
389 FS 'MO'
F-16C Block 52P
Deployment: OSW
Unknown
[act]
92889
389 FS 'MO'
F-16C Block 52P
Nov 2001
[act]
92889
389 FS 'MO'
F-16C Block 52P
"Vulture, T-bolts rule"
Special characteristics:
Nose Art
Mission Marks
Deployment: OEF
Comments: 12 mission markings for Operation Enduring Freedom. Art work by TSgt Robbie Leist and SSgt Chad Marks.
Comments: 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.
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.