Narrative:

On takeoff roll at ewn saw previously unannounced high-winged small aircraft inbound to opp runway from the runway we were departing on. We were departing runway 22 small aircraft was apparently flying ILS for runway 04 at ewn. We were IFR with release from cherry point approach via ewn radio (FSS 123.65). Saw traffic right at V1 and elected to continue. Takeoff and break to right to avoid traffic. Commenced turn immediately after rotation. FSS radio operator stated, 'I don't know where he came from.' asked cherry point approach about the traffic just avoided and was told he had been worked by cherry point and had been cleared for the ILS 04 ewn, but that controller had thought the small aircraft would be going full procedure (outbnd then inbound). Instead small aircraft just proceeded straight in resulting in traffic conflict. When I first saw small aircraft I would estimate he was at approximately 400' AGL and 1/2 mi final (to opp runway). Winds were favoring runway 22 with approximately 10 KT headwind component. Throughout taxi out and departure roll we maintained listening watch on CTAF (123.65) and announced taxi-out and takeoff. No xmissions were heard from small aircraft. Estimate our distance to small aircraft was 2000' horizontal and 100' vertical at closest passing. I would described my turn to avoid traffic as evasive action. While I realize that the ultimate responsibility to see and avoid falls on the flight crews there have been enough failures of the see and avoid system, particularly on airports or in immediate airport environment to suggest the shortcomings of this system, try as we all do. Pilots can use all the help that they can get. In this case we might have gotten a little more help from cherry point who could have noticed (must have noticed?) that the small aircraft was proceeding straight inbound as he had not anticipated and was straight in for the opp runway he had just released us from. The approach controller might have called FSS and had the FSS gave us a heads-up. Worth noting that we did scan the horizon before taking runway, but simply failed to pick up small aircraft. As the aircraft was pointed straight at us it would have presented a very narrow straight on profile with no relative movement. A control tower operation at ewn would sure help.

Related reports:

Google
 

Original NASA ASRS Text

Title: CLOSE PROX COMMUTER-LTT GA-SMA OVER EWN.

Narrative: ON TKOF ROLL AT EWN SAW PREVIOUSLY UNANNOUNCED HIGH-WINGED SMA INBND TO OPP RWY FROM THE RWY WE WERE DEPARTING ON. WE WERE DEPARTING RWY 22 SMA WAS APPARENTLY FLYING ILS FOR RWY 04 AT EWN. WE WERE IFR WITH RELEASE FROM CHERRY POINT APCH VIA EWN RADIO (FSS 123.65). SAW TFC RIGHT AT V1 AND ELECTED TO CONTINUE. TKOF AND BREAK TO RIGHT TO AVOID TFC. COMMENCED TURN IMMEDIATELY AFTER ROTATION. FSS RADIO OPERATOR STATED, 'I DON'T KNOW WHERE HE CAME FROM.' ASKED CHERRY POINT APCH ABOUT THE TFC JUST AVOIDED AND WAS TOLD HE HAD BEEN WORKED BY CHERRY POINT AND HAD BEEN CLRED FOR THE ILS 04 EWN, BUT THAT CTLR HAD THOUGHT THE SMA WOULD BE GOING FULL PROC (OUTBND THEN INBND). INSTEAD SMA JUST PROCEEDED STRAIGHT IN RESULTING IN TFC CONFLICT. WHEN I FIRST SAW SMA I WOULD ESTIMATE HE WAS AT APPROX 400' AGL AND 1/2 MI FINAL (TO OPP RWY). WINDS WERE FAVORING RWY 22 WITH APPROX 10 KT HEADWIND COMPONENT. THROUGHOUT TAXI OUT AND DEP ROLL WE MAINTAINED LISTENING WATCH ON CTAF (123.65) AND ANNOUNCED TAXI-OUT AND TKOF. NO XMISSIONS WERE HEARD FROM SMA. ESTIMATE OUR DISTANCE TO SMA WAS 2000' HORIZ AND 100' VERT AT CLOSEST PASSING. I WOULD DESCRIBED MY TURN TO AVOID TFC AS EVASIVE ACTION. WHILE I REALIZE THAT THE ULTIMATE RESPONSIBILITY TO SEE AND AVOID FALLS ON THE FLT CREWS THERE HAVE BEEN ENOUGH FAILURES OF THE SEE AND AVOID SYS, PARTICULARLY ON ARPTS OR IN IMMEDIATE ARPT ENVIRONMENT TO SUGGEST THE SHORTCOMINGS OF THIS SYS, TRY AS WE ALL DO. PLTS CAN USE ALL THE HELP THAT THEY CAN GET. IN THIS CASE WE MIGHT HAVE GOTTEN A LITTLE MORE HELP FROM CHERRY POINT WHO COULD HAVE NOTICED (MUST HAVE NOTICED?) THAT THE SMA WAS PROCEEDING STRAIGHT INBND AS HE HAD NOT ANTICIPATED AND WAS STRAIGHT IN FOR THE OPP RWY HE HAD JUST RELEASED US FROM. THE APCH CTLR MIGHT HAVE CALLED FSS AND HAD THE FSS GAVE US A HEADS-UP. WORTH NOTING THAT WE DID SCAN THE HORIZON BEFORE TAKING RWY, BUT SIMPLY FAILED TO PICK UP SMA. AS THE ACFT WAS POINTED STRAIGHT AT US IT WOULD HAVE PRESENTED A VERY NARROW STRAIGHT ON PROFILE WITH NO RELATIVE MOVEMENT. A CTL TWR OPERATION AT EWN WOULD SURE HELP.

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.