Narrative:

After takeoff on runway 34R out of slc, we were climbing out on the SID to the north towards hill AFB when departure control informed us of VFR traffic to our right, 1-2 O'clock position. We visually acquired the traffic over the mountains which lie to the east of slc and hill AFB. I remarked to the captain that the traffic appeared to be a fast mover. We watched the aircraft turn toward us rapidly. Our TCASII soon responded with a TA and then shortly followed by an RA. The captain (PF) followed the commands given by the TCASII in this rapidly developing near midair. The VFR traffic turned out to be an F16. The F16 was on a collision course with our aircraft until last second maneuvering by the F16 and our response to the TCASII. The F16 passed down the first officer's side of aircraft, slightly high and belly up to us. The fighter was close enough to use that we could hear his engine as he passed us. We told ATC that we had responded to an RA due to the F16. ATC then informed us that the F16 was in a simulated flameout pattern at hill AFB. Even though we had the VFR traffic visually, it was difficult to determine his flight path and predict his future flight path. With his speed and maneuverability, he rapidly changed from no threat to a major safety concern. When we first obtained our visual, he was higher, parallel to us, and heading the same direction. Thankfully, we kept him in sight and did not disregard him as no threat. Mixing of military high performance, VFR traffic and loaded passenger, departing IFR traffic at slc should be addressed. I have doubts that the F16 pilot was aware of our existence until the last couple of seconds.

Google
 

Original NASA ASRS Text

Title: L1011 AND MIL F16 HAD NMAC NEAR HIF.

Narrative: AFTER TKOF ON RWY 34R OUT OF SLC, WE WERE CLBING OUT ON THE SID TO THE N TOWARDS HILL AFB WHEN DEP CTL INFORMED US OF VFR TFC TO OUR R, 1-2 O'CLOCK POS. WE VISUALLY ACQUIRED THE TFC OVER THE MOUNTAINS WHICH LIE TO THE E OF SLC AND HILL AFB. I REMARKED TO THE CAPT THAT THE TFC APPEARED TO BE A FAST MOVER. WE WATCHED THE ACFT TURN TOWARD US RAPIDLY. OUR TCASII SOON RESPONDED WITH A TA AND THEN SHORTLY FOLLOWED BY AN RA. THE CAPT (PF) FOLLOWED THE COMMANDS GIVEN BY THE TCASII IN THIS RAPIDLY DEVELOPING NEAR MIDAIR. THE VFR TFC TURNED OUT TO BE AN F16. THE F16 WAS ON A COLLISION COURSE WITH OUR ACFT UNTIL LAST SECOND MANEUVERING BY THE F16 AND OUR RESPONSE TO THE TCASII. THE F16 PASSED DOWN THE FO'S SIDE OF ACFT, SLIGHTLY HIGH AND BELLY UP TO US. THE FIGHTER WAS CLOSE ENOUGH TO USE THAT WE COULD HEAR HIS ENG AS HE PASSED US. WE TOLD ATC THAT WE HAD RESPONDED TO AN RA DUE TO THE F16. ATC THEN INFORMED US THAT THE F16 WAS IN A SIMULATED FLAMEOUT PATTERN AT HILL AFB. EVEN THOUGH WE HAD THE VFR TFC VISUALLY, IT WAS DIFFICULT TO DETERMINE HIS FLT PATH AND PREDICT HIS FUTURE FLT PATH. WITH HIS SPD AND MANEUVERABILITY, HE RAPIDLY CHANGED FROM NO THREAT TO A MAJOR SAFETY CONCERN. WHEN WE FIRST OBTAINED OUR VISUAL, HE WAS HIGHER, PARALLEL TO US, AND HDG THE SAME DIRECTION. THANKFULLY, WE KEPT HIM IN SIGHT AND DID NOT DISREGARD HIM AS NO THREAT. MIXING OF MIL HIGH PERFORMANCE, VFR TFC AND LOADED PAX, DEPARTING IFR TFC AT SLC SHOULD BE ADDRESSED. I HAVE DOUBTS THAT THE F16 PLT WAS AWARE OF OUR EXISTENCE UNTIL THE LAST COUPLE OF SECONDS.

Data retrieved from NASA's ASRS site as of July 2007 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.