Community
Crew Chief Profiles
SSgt.
Scott
"
Elvis"
Gandy
My profile
![]() |
Name | SSgt. Scott Gandy |
Country |
![]() |
|
Unit | 33rd Fighter Squadron "Falcons" | |
Crewing F-16s | from 1984 until 1994 | |
Contact Elvis | Send me a private message | |
Website | ||
Shaw AFB- 33d AMU 1984-1989 F-16C Block 25 Kunsan AB- 35th AMU 1990-1991 Block 30 Hill AFB- 2952/649 CLSS 1991-1994 Block 1/5/15/25/30/40/50, F-4 Then offered assignment to Sheppard, with the option to say no with the condition that I got out.. Well, the SSB was the way to go..I was hired the next day by McDonnell Douglas on the MD-90 program, after that, I went to Southwest Airlines as an A&P and was there for 14 years, also worked as an Avionics Engineer for 5 years, then a Maintenance Controller for 3 and a half years, then as an Aircraft Maintenance Supervisor in Las Vegas.. No ifs, ands, or buts the best place to crew jets. Retired from SWA in 2009, now with the FAA Transport Aircraft Evaluation Group remotely sited in SLC. Current or Favourite assignmentFirst operational unit with the F-16C, lots of those pilots fly for us now..The best assignment hands down was CLSS, you do it all there, and learn many skills that you will use later on |
My Jets & Assignments
![]() |
83143 | [Detailed history of this F-16] | ||||
Unit | 33rd Fighter Squadron "Falcons" | [Unit History] | ||||
Period | 1985 - 1986 | |||||
Current: | 83143 | ![]() |
F-16C Block 25 | [ i/a] | ||
Brand new from the factory, jet was later assigned to Eglin AFB for ASPJ testing, now a trainer at Sheppard.. Now that'd make you feel old!! Left Shaw with the same engine it was delivered with!! | ||||||
![]() |
84281 | [Detailed history of this F-16] | ||||
Unit | 33rd Fighter Squadron "Falcons" | [Unit History] | ||||
Period | 1987 - 1989 | |||||
Current: | ![]() |
F-16C Block 25 | [ i/a] | |||
Best damn jet in the fleet!! In stats that is.. | ||||||
![]() |
86208 | [Detailed history of this F-16] | ||||
Unit | 35th Fighter Squadron "Pantons" | [Unit History] | ||||
Period | 1990 - 1990 | |||||
Current: | AAFG0653 | ![]() |
F-16C Block 30 | [ sto] | ||
One of the two "small mouth" jets in the 35th, what a pain in the butt when it came to engine runs, but all in all a good jet.. | ||||||
![]() |
79419 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1991 - 1991 | |||||
Current: | 79419 | ![]() |
F-16B Block 5 | [ w/o] | ||
Was on crew that rebuilt after mid-air collision with F-15, jet was later lost on night low level at UTTR | ||||||
![]() |
80560 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1991 - 1991 | |||||
Current: | AAFG0268 | ![]() |
F-16A Block 15 ADF | [ sto] | ||
![]() |
84382 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1991 - 1994 | |||||
Current: | 84382 | ![]() |
F-16C Block 25 | [ sto] | ||
Had to recover from Hahn AB after a fire on the runway, burned the lower aft fuselage | ||||||
![]() |
78019 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1992 - 1994 | |||||
Current: | 78019 | ![]() |
F-16A Block 1 | [ scr] | ||
We rebuilt this one for the 3rd time after fire damage to aft fuselage, this was the first F-16 to be rebuilt after it ran off the runway at SLC | ||||||
|
88495 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1991 - 1992 | |||||
Current: | 88495 | ![]() |
F-16C Block 40 | [ act] | ||
On crew rebuilding after damage from SA-2 hit over Iraq | ||||||
![]() |
88456 | [Detailed history of this F-16] | ||||
Unit | 649 CLSS | |||||
Period | 1993 - 1993 | |||||
Current: | 88456 | ![]() |
F-16C Block 42 | [ act] | ||
Rebuilt after gear-up landing at Edwards, was Block 50 test-bed jet, also converted from a small-mouth to big-mouth configuration. Great project! |
Visitor Comments
Do you hear from.
meandean,
Oct 11, 2010 - 08:30 PM

Hi Scott, Do you hear from Linda F. Just curious haven't talked to anyone in years.
Dean Collins
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.