Narrative:

We (aircraft X) were a scheduled air carrier departure, using runway 8. There were some military aircraft in the pattern. A C130 was doing touch-and-goes on runway 3R. An F16 (aircraft Y) was doing low passes on runway 3. We had seen 2 harriers do a low pass in formation earlier. Our clearance out of yum was mohak departure with a climb to 4000 ft. At XA05 we were cleared for takeoff from runway 8 and told to fly runway heading. The first officer was the PF, I handled the radios. We were handed off from tower to departure control right after liftoff. As we were climbing out from runway 8 on runway heading at 1500 ft, I saw this fast moving jet military fighter (aircraft Y) come at us from our left. I told the first officer to level off immediately. At the same time the departure controller told us to maintain 1200 ft. I told her we had traffic in sight and that we were descending to 1200 ft. After about 1 min, she told us that we were clear of traffic and cleared us to climb again. There was no further comment or explanation from the controller. We were then handed off to the next frequency. This situation was clearly a controller error due to miscom between tower and departure controller or lack of situational awareness among the controllers. We managed to avoid a midair collision due to our own vigilance. There were no TCASII alerts -- jet probably had transponder turned off. This event showas us the importance of the see and avoid concept and not to trust technology such as TCASII and/or rely too much on controllers. This near midair collision could have been totally avoided had the tower controller told us about the traffic and/or communicated this to departure controller. Departure controller should have known about the traffic and alerted us to the fact sooner. Callback conversation with reporter revealed the following information: reporter was extra cautious on departure because of the observed aircraft activity in the area. The reporter did not provide company with a follow-up of the incident.

Google
 

Original NASA ASRS Text

Title: DHC8 FLC INITIATE EVASIVE MANEUVER ON DEP WHEN OBSERVING AN F16 FROM ANOTHER INTERSECTING YUM RWY COME INTO CONFLICT WITH THEM.

Narrative: WE (ACFT X) WERE A SCHEDULED ACR DEP, USING RWY 8. THERE WERE SOME MIL ACFT IN THE PATTERN. A C130 WAS DOING TOUCH-AND-GOES ON RWY 3R. AN F16 (ACFT Y) WAS DOING LOW PASSES ON RWY 3. WE HAD SEEN 2 HARRIERS DO A LOW PASS IN FORMATION EARLIER. OUR CLRNC OUT OF YUM WAS MOHAK DEP WITH A CLB TO 4000 FT. AT XA05 WE WERE CLRED FOR TKOF FROM RWY 8 AND TOLD TO FLY RWY HDG. THE FO WAS THE PF, I HANDLED THE RADIOS. WE WERE HANDED OFF FROM TWR TO DEP CTL RIGHT AFTER LIFTOFF. AS WE WERE CLBING OUT FROM RWY 8 ON RWY HDG AT 1500 FT, I SAW THIS FAST MOVING JET MIL FIGHTER (ACFT Y) COME AT US FROM OUR L. I TOLD THE FO TO LEVEL OFF IMMEDIATELY. AT THE SAME TIME THE DEP CTLR TOLD US TO MAINTAIN 1200 FT. I TOLD HER WE HAD TFC IN SIGHT AND THAT WE WERE DSNDING TO 1200 FT. AFTER ABOUT 1 MIN, SHE TOLD US THAT WE WERE CLR OF TFC AND CLRED US TO CLB AGAIN. THERE WAS NO FURTHER COMMENT OR EXPLANATION FROM THE CTLR. WE WERE THEN HANDED OFF TO THE NEXT FREQ. THIS SIT WAS CLRLY A CTLR ERROR DUE TO MISCOM BTWN TWR AND DEP CTLR OR LACK OF SITUATIONAL AWARENESS AMONG THE CTLRS. WE MANAGED TO AVOID A MIDAIR COLLISION DUE TO OUR OWN VIGILANCE. THERE WERE NO TCASII ALERTS -- JET PROBABLY HAD XPONDER TURNED OFF. THIS EVENT SHOWAS US THE IMPORTANCE OF THE SEE AND AVOID CONCEPT AND NOT TO TRUST TECHNOLOGY SUCH AS TCASII AND/OR RELY TOO MUCH ON CTLRS. THIS NMAC COULD HAVE BEEN TOTALLY AVOIDED HAD THE TWR CTLR TOLD US ABOUT THE TFC AND/OR COMMUNICATED THIS TO DEP CTLR. DEP CTLR SHOULD HAVE KNOWN ABOUT THE TFC AND ALERTED US TO THE FACT SOONER. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR WAS EXTRA CAUTIOUS ON DEP BECAUSE OF THE OBSERVED ACFT ACTIVITY IN THE AREA. THE RPTR DID NOT PROVIDE COMPANY WITH A FOLLOW-UP OF THE INCIDENT.

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.