Crew Chief Profiles

 TSgt. Brian "BC" Curtis (Ret.)

My profile

Name TSgt. Brian Curtis (Ret.)
Country
Unit 1st Wing "Falcon"
Crewing F-16s from 1986 until 2006
Contact BrianCurtis Send me a private message
Website
Started with the 72 at MacDill, then went to the Kun and spent a year in the tree with the 35th. Ended back at MacDill to close out the 72. Transfered to the 61st to help close that one down then moved to Luke to startup the 62. Then the Air Force decided I needed to move again and sent me back to Kunsan where I ended up in the 35 and on the same jet as before. Well someone must of thought that was funny because I ended badk at Luke in the 62 again. Decided that was so much fun I was going to QA for a while. Did the tour in QA and after that it seems that I was wanted in the 61 to expedite and be the Asst Flt Chief. Then I decided that i was done playing and retired in AZ. Now getting ready to move to Atl Ga.

My Jets & Assignments

78079 [Detailed history of this F-16]
Unit 72nd Fighter Squadron "Falcons" [Unit History]
Period 1986 - 1990
Current: AAFG0240  USAF AMARC F-16B Block 1 [sto]
One of the best group of guys to work with, Bflt swing shift with Dave McPhereson (sp) as the flt chief. Of course who could forget Chef Diaz and the fact we couldnt keep a flagship.
86301 [Detailed history of this F-16]
Unit 35th Fighter Squadron "Pantons" [Unit History]
Period 1990 - 1991
Current: 86301  USAF 18 AGRS F-16C Block 30 [act]
The Tree, that was the place to be!! 301 was the 35th sq flagship when I was there.
84396 [Detailed history of this F-16]
Unit 72nd Fighter Squadron "Falcons" [Unit History]
Period 1991 - 1993
Current: 84396  USAF 309 FS F-16D Block 25 [act]
Started in the 72 but only to help transfer out the equip. Moved to the 61 and was the asst on 87261. Yes the 61st, land of Bill Hindi on a fri night saying ( I think my ADG is using too much oil, lets troubleshoot it. Of course I dont think we ever found a problem.) Tim Stavely thanks for all the education on the Flt line and the Golf course!!
83161 [Detailed history of this F-16]
Unit 62nd Fighter Squadron "Spikes" [Unit History]
Period 1993 - 1999
Current: AAFG0618  USAF AMARC F-16C Block 25 [sto]
Shut 2 squadrons down in Fl. Time to start one up at Luke. Nothing like having to drive down to Gila Bend because the EPA would let the jets into Luke. In that time span I was the owner of acft 83-161, 85-1512, 84-1382, and 84-1296 yep I was a sq flagship puke. Just dont mess with my assistant Big Louie!!!
86301 [Detailed history of this F-16]
Unit 35th Fighter Squadron "Pantons" [Unit History]
Period 1999 - 2000
Current: 86301  USAF 18 AGRS F-16C Block 30 [act]
Talk about Dejavu! Same flippin sq, same jet, just no tree instead you get HAS 19 theres no lights or a door so have fun!!Oh by the way you and Pops Warner are the only 7 lvls and theres no flt chief so make sure everythings taken care for dayshift.
84222 [Detailed history of this F-16]
Unit 62nd Fighter Squadron "Spikes" [Unit History]
Period 2000 - 2006
Current: QF-009  USAF 82 ATRS QF-16C Block 25 [des]
Did the 62 thing again for a year then transfered to QA ,nothing beats the feeling of having your golf cart nice and clean. After that I ended up in the 61 to expedite and asst flt chief oh by the way Brian your in charge of training for the Flt. so get your CBT done!!

Visitor Comments

looking for crew chiefs
Darren Key, Jun 02, 2009 - 08:19 AM

I was a crew chief at the 62nd Fighter SQ back in 1996-1999..........I would like to find some of those guys I used to work with.

I used to work with you, sometimes
Don Schaaf, Nov 03, 2009 - 08:09 PM

Even though I am a pointy-head, you didn't actually despise me that much. How you doin', bro? Are you still at Luke? I'm at the Kun, and will be at Spang in Feb, with the wife and 5.4 kids (yes, #6 is on the way, we'll name this one MidTour).

You're still alive?
Dan Lucero, Dec 11, 2009 - 07:06 PM

Hey there BC. I was sad to see your comments didn't mention the awesome engine guys you worked with. Anyway, I hope you're enjoying your time off.

Leave a comment





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.