Narrative:

I was working the paine sector but I was watching departure as well during periods of non-activity. I noticed an air show aircraft coming very close to the edge of the air show tfr. Then a departure came off seattle northbound. I observed a fighter jet aerial demo aircraft come within about 3/4 of a mile and 600 ft or less of the departing air carrier. He was also traveling at a speed (approximately 450 KTS) where the air carrier could not have made any maneuvers to avoid him. It appears to me that these pilots have not been properly briefed on the risks and traps of flying within the seattle airspace. Avoiding seatac should have been the top priority during the planning and morning briefs with these air show pilots. This was a very dangerous situation. The pilots should have been better prepared and briefed by the lead ATC representative on how to depart and return to their airport safely. At a minimum they should at all times know where they are reference the seattle flow of traffic. Controllers; air-boss; pilots and ATC representatives need to be on the same page on how to work these guys. It's seriously poor planning that this situation occurred. Pilot should fly at a safe speed. Lastly; a flm said that he told all aircraft to turn off their transponders while in the tfr; this seems wrong. There is no separation built in with a tfr. They can run right up to the border and non participating aircraft can run up to the outside border; so where is the separation? It seems to me like a transponder might be the only thing that separates two aircraft. The air carrier had no idea that the the fighter jet was there because his transponder was off. Had it been on; the air carrier at least may have been able to see him coming and take evasive action if he felt that was necessary. This wasn't a big deal this time because they missed but it could have been much worse. And worst of all; it could have been prevented.

Google
 

Original NASA ASRS Text

Title: S46 Controller described an unsafe event when a military fighter participating in an air show transitioned very close to the TFR boundary in close proximity to departure traffic. The reporter voiced concern regarding the FAA's 'no transponder policy' issued to air show participants.

Narrative: I was working the Paine Sector but I was watching Departure as well during periods of non-activity. I noticed an air show aircraft coming very close to the edge of the air show TFR. Then a departure came off Seattle northbound. I observed a fighter jet aerial demo aircraft come within about 3/4 of a mile and 600 FT or less of the departing Air Carrier. He was also traveling at a speed (approximately 450 KTS) where the Air Carrier could not have made any maneuvers to avoid him. It appears to me that these pilots have not been properly briefed on the risks and traps of flying within the Seattle airspace. Avoiding SEATAC should have been the top priority during the planning and morning briefs with these air show pilots. This was a very dangerous situation. The pilots should have been better prepared and briefed by the lead ATC representative on how to depart and return to their airport safely. At a minimum they should at all times know where they are reference the Seattle flow of traffic. Controllers; Air-boss; pilots and ATC representatives need to be on the same page on how to work these guys. It's seriously poor planning that this situation occurred. Pilot should fly at a safe speed. Lastly; a FLM said that he told all aircraft to turn off their transponders while in the TFR; this seems wrong. There is no separation built in with a TFR. They can run right up to the border and non participating aircraft can run up to the outside border; so where is the separation? It seems to me like a transponder might be the only thing that separates two aircraft. The Air Carrier had no idea that the the fighter jet was there because his transponder was off. Had it been on; the Air Carrier at least may have been able to see him coming and take evasive action if he felt that was necessary. This wasn't a big deal this time because they missed but it could have been much worse. And worst of all; it could have been prevented.

Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.