Narrative:

Departed ewr runway 29 VFR to avp. While we were still in ewr's air traffic area, the controller said to proceed 'on course' to avp. Approximately 8 NM northwest of ewr radar service was terminated. We observed opposite direction traffic on our TCASII and soon picked the traffic up visually. I descended to avoid a collision (RA on TCASII gave us 'descend') and the aircraft passed overhead approximately 200 - 300 ft. While preoccupied with that traffic, we found ourselves in the mmu air traffic area. (Note -- the ceiling of the mmu air traffic area and the floor of the ewr TCA coincide. Both ewr and mmu air traffic area's are separated by only a few mi and it was during this short distance after our radar service was terminated we became preoccupied with the traffic/TCASII RA). Do not assume that the controller's 'on course' will include handoff communication to an adjacent air traffic area (as in this situation) in the event radar service is terminated. We were on duty for almost 12 hours and this was the seventh leg of an 8 leg day. Decision making could be affected by fatigue. Supplemental information from acn 270615: a saab 340 passed above us opposite direction off our left. I called back to ewr departure for a frequency. Spoke to next controller who stated we should have contacted morristown control tower to transition for future reference. I feel I was led down this path by ewr departure controller who did not warn me of morristown airport. By the time he switched me and because of TA on TCASII, I was locked in my inability to climb. Even without TCASII alert, I was too close to morristown to do anything but fly overhead. Our company has not issued VFR charts and our company manual states we can use low altitude en route charts for VFR navigating.

Google
 

Original NASA ASRS Text

Title: NMAC BTWN 2 ACR OPPOSITE DIRECTION TFC. COMMUTER OPS. PROX OF MULTIPLE ARPTS. SEE AND AVOID CONCEPT INADEQUATE IN THESE CIRCUMSTANCES.

Narrative: DEPARTED EWR RWY 29 VFR TO AVP. WHILE WE WERE STILL IN EWR'S ATA, THE CTLR SAID TO PROCEED 'ON COURSE' TO AVP. APPROX 8 NM NW OF EWR RADAR SVC WAS TERMINATED. WE OBSERVED OPPOSITE DIRECTION TFC ON OUR TCASII AND SOON PICKED THE TFC UP VISUALLY. I DSNDED TO AVOID A COLLISION (RA ON TCASII GAVE US 'DSND') AND THE ACFT PASSED OVERHEAD APPROX 200 - 300 FT. WHILE PREOCCUPIED WITH THAT TFC, WE FOUND OURSELVES IN THE MMU ATA. (NOTE -- THE CEILING OF THE MMU ATA AND THE FLOOR OF THE EWR TCA COINCIDE. BOTH EWR AND MMU ATA'S ARE SEPARATED BY ONLY A FEW MI AND IT WAS DURING THIS SHORT DISTANCE AFTER OUR RADAR SVC WAS TERMINATED WE BECAME PREOCCUPIED WITH THE TFC/TCASII RA). DO NOT ASSUME THAT THE CTLR'S 'ON COURSE' WILL INCLUDE HDOF COM TO AN ADJACENT ATA (AS IN THIS SIT) IN THE EVENT RADAR SVC IS TERMINATED. WE WERE ON DUTY FOR ALMOST 12 HRS AND THIS WAS THE SEVENTH LEG OF AN 8 LEG DAY. DECISION MAKING COULD BE AFFECTED BY FATIGUE. SUPPLEMENTAL INFO FROM ACN 270615: A SAAB 340 PASSED ABOVE US OPPOSITE DIRECTION OFF OUR L. I CALLED BACK TO EWR DEP FOR A FREQ. SPOKE TO NEXT CTLR WHO STATED WE SHOULD HAVE CONTACTED MORRISTOWN CTL TWR TO TRANSITION FOR FUTURE REF. I FEEL I WAS LED DOWN THIS PATH BY EWR DEP CTLR WHO DID NOT WARN ME OF MORRISTOWN ARPT. BY THE TIME HE SWITCHED ME AND BECAUSE OF TA ON TCASII, I WAS LOCKED IN MY INABILITY TO CLB. EVEN WITHOUT TCASII ALERT, I WAS TOO CLOSE TO MORRISTOWN TO DO ANYTHING BUT FLY OVERHEAD. OUR COMPANY HAS NOT ISSUED VFR CHARTS AND OUR COMPANY MANUAL STATES WE CAN USE LOW ALT ENRTE CHARTS FOR VFR NAVIGATING.

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.