Narrative:

A B737-200, operated by air carrier in part 121 scheduled service was departing jax. On the flight deck, as first officer, I was performing normal PNF duties. Taxi and takeoff were uneventful. Immediately prior to our takeoff clearance, 2 F15 type fighter aircraft made a low pass to runway 25 and remained in closed traffic. Our takeoff run, liftoff, and climb out from runway 25 was normal. During our climb (approximately 600 ft AGL) I heard the roar of jet engines. I turned to check my 5 O'clock position and saw the underside of an F15 at our altitude. I estimate the range to be on the order of 500-1000 ft. Returning to forward scan I reported the traffic to the captain. The captain was established in approximately a 15 degree bank (in response to ATC to turn right to a heading of 310 degrees). The captain arrested his turn. I turned once again looking for the traffic, this time the F15 at 4 O'clock, in approximately a 70 degree bank, in what appeared to be full afterburner. He was accelerating rapidly away from our position. Our flight attendants also reported hearing the roar of the F15 in the main cabin. 1) when instructing the fighter aircraft, ATC may not have been specific in regard to our position. 2) the fighter pilot (high single pilot workload) may not have seen our aircraft until closing rapidly (shared use airspace?). 3) no TCASII RA/TA was received. (F15 not squawking?, equipment failure?, equipment inhibit function below 1000 ft AGL?). Callback conversation with reporter revealed the following information: reporter called back with the following information. The PIC was flying the aircraft and was very concerned with the issues of this event. He later called the tower controller when the flight arrived at its destination airport. The first officer reporter was not privy to what was said except that the tower controller seemed, to the captain, to be quite unconcerned with the incident. The controller said that this was a 'normal' event. The controller had issued a TA to the military pilots regarding the B737 on takeoff and that both military aircraft were on a second low pass on the go around fly-by. There was not any air show activity going on at this time. The first officer said that the roar of the jet engines on the near midair collision was incredible and felt that the passenger may have also been alarmed. However, there were no adverse comments by the passenger upon their deplaning. Supplemental information from acn 362697: some way must be found to keep high performance fighter aircraft away from civilian aircraft with innocent non combat passenger aboard. Apparently, legal separation means 'no merging of aircraft.' 1 ft separation is as good as 1 mi to ZJX! Parties notified: jax tower by phone, mr Z. ZTL region by phone, mr X. Dispatch, in person. Chief pilot, captain Y, in person and in writing. FAA principal inspector, in person.

Google
 

Original NASA ASRS Text

Title: NMAC OCCURS AS ACR B737-200 IS STARTED IN A R TURN DURING INITIAL CLB AND AN F15 FIGHTER CLOSES ON THE R DURING A RWY FLY OVER OR GAR.

Narrative: A B737-200, OPERATED BY ACR IN PART 121 SCHEDULED SVC WAS DEPARTING JAX. ON THE FLT DECK, AS FO, I WAS PERFORMING NORMAL PNF DUTIES. TAXI AND TKOF WERE UNEVENTFUL. IMMEDIATELY PRIOR TO OUR TKOF CLRNC, 2 F15 TYPE FIGHTER ACFT MADE A LOW PASS TO RWY 25 AND REMAINED IN CLOSED TFC. OUR TKOF RUN, LIFTOFF, AND CLBOUT FROM RWY 25 WAS NORMAL. DURING OUR CLB (APPROX 600 FT AGL) I HEARD THE ROAR OF JET ENGS. I TURNED TO CHK MY 5 O'CLOCK POS AND SAW THE UNDERSIDE OF AN F15 AT OUR ALT. I ESTIMATE THE RANGE TO BE ON THE ORDER OF 500-1000 FT. RETURNING TO FORWARD SCAN I RPTED THE TFC TO THE CAPT. THE CAPT WAS ESTABLISHED IN APPROX A 15 DEG BANK (IN RESPONSE TO ATC TO TURN R TO A HDG OF 310 DEGS). THE CAPT ARRESTED HIS TURN. I TURNED ONCE AGAIN LOOKING FOR THE TFC, THIS TIME THE F15 AT 4 O'CLOCK, IN APPROX A 70 DEG BANK, IN WHAT APPEARED TO BE FULL AFTERBURNER. HE WAS ACCELERATING RAPIDLY AWAY FROM OUR POS. OUR FLT ATTENDANTS ALSO RPTED HEARING THE ROAR OF THE F15 IN THE MAIN CABIN. 1) WHEN INSTRUCTING THE FIGHTER ACFT, ATC MAY NOT HAVE BEEN SPECIFIC IN REGARD TO OUR POS. 2) THE FIGHTER PLT (HIGH SINGLE PLT WORKLOAD) MAY NOT HAVE SEEN OUR ACFT UNTIL CLOSING RAPIDLY (SHARED USE AIRSPACE?). 3) NO TCASII RA/TA WAS RECEIVED. (F15 NOT SQUAWKING?, EQUIP FAILURE?, EQUIP INHIBIT FUNCTION BELOW 1000 FT AGL?). CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR CALLED BACK WITH THE FOLLOWING INFO. THE PIC WAS FLYING THE ACFT AND WAS VERY CONCERNED WITH THE ISSUES OF THIS EVENT. HE LATER CALLED THE TWR CTLR WHEN THE FLT ARRIVED AT ITS DEST ARPT. THE FO RPTR WAS NOT PRIVY TO WHAT WAS SAID EXCEPT THAT THE TWR CTLR SEEMED, TO THE CAPT, TO BE QUITE UNCONCERNED WITH THE INCIDENT. THE CTLR SAID THAT THIS WAS A 'NORMAL' EVENT. THE CTLR HAD ISSUED A TA TO THE MIL PLTS REGARDING THE B737 ON TKOF AND THAT BOTH MIL ACFT WERE ON A SECOND LOW PASS ON THE GAR FLY-BY. THERE WAS NOT ANY AIR SHOW ACTIVITY GOING ON AT THIS TIME. THE FO SAID THAT THE ROAR OF THE JET ENGS ON THE NMAC WAS INCREDIBLE AND FELT THAT THE PAX MAY HAVE ALSO BEEN ALARMED. HOWEVER, THERE WERE NO ADVERSE COMMENTS BY THE PAX UPON THEIR DEPLANING. SUPPLEMENTAL INFO FROM ACN 362697: SOME WAY MUST BE FOUND TO KEEP HIGH PERFORMANCE FIGHTER ACFT AWAY FROM CIVILIAN ACFT WITH INNOCENT NON COMBAT PAX ABOARD. APPARENTLY, LEGAL SEPARATION MEANS 'NO MERGING OF ACFT.' 1 FT SEPARATION IS AS GOOD AS 1 MI TO ZJX! PARTIES NOTIFIED: JAX TWR BY PHONE, MR Z. ZTL REGION BY PHONE, MR X. DISPATCH, IN PERSON. CHIEF PLT, CAPT Y, IN PERSON AND IN WRITING. FAA PRINCIPAL INSPECTOR, IN PERSON.

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.