37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 357640 |
Time | |
Date | 199701 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ewn |
State Reference | NC |
Altitude | msl bound lower : 700 msl bound upper : 700 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : nkt |
Operator | common carrier : air taxi |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 135 |
Flight Phase | climbout : initial climbout : intermediate altitude cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Experience | flight time last 90 days : 100 flight time total : 3500 flight time type : 100 |
ASRS Report | 357640 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I departed runway 22 at ewn, nc, on an instrument flight plan. Shortly after lift-off, I noticed what appeared to be traffic approaching low from the southwest. The area in this direction is mostly swamp and national forest. Prior to changing over from unicom 123.65 to cherry point approach 119.35 I decided to turn away from the traffic to the left. I continued the turn 270 degrees around. In the middle over the turn I contacted cherry point approach. The controller cleared me to altitude and course. He also inquired about my turn to the left after departure, at which time it became clear that the conflict traffic was either a tower or helicopter traffic. There was no reported traffic on the unicom frequency, and cherry point approach control did not see any either. I could have contacted cherry point approach first prior to turning, however, our crossing of flight paths appeared imminent. I felt the prudent thing to do was simply turn in the pattern and depart overhead of the airport. The WX was good VFR at the time.
Original NASA ASRS Text
Title: SMT ACFT ON DEP AT NIGHT MISIDENTED LIGHTS AS INTRUDER ACFT AND TURNED AWAY FOR AVOIDANCE, BUT NOT IN ACCORDANCE WITH IFR CLRNC. TRACON CTLR QUESTIONED THE TURN AFTER RPTR CHKED IN WITH HIM.
Narrative: I DEPARTED RWY 22 AT EWN, NC, ON AN INST FLT PLAN. SHORTLY AFTER LIFT-OFF, I NOTICED WHAT APPEARED TO BE TFC APCHING LOW FROM THE SW. THE AREA IN THIS DIRECTION IS MOSTLY SWAMP AND NATIONAL FOREST. PRIOR TO CHANGING OVER FROM UNICOM 123.65 TO CHERRY POINT APCH 119.35 I DECIDED TO TURN AWAY FROM THE TFC TO THE L. I CONTINUED THE TURN 270 DEGS AROUND. IN THE MIDDLE OVER THE TURN I CONTACTED CHERRY POINT APCH. THE CTLR CLRED ME TO ALT AND COURSE. HE ALSO INQUIRED ABOUT MY TURN TO THE L AFTER DEP, AT WHICH TIME IT BECAME CLR THAT THE CONFLICT TFC WAS EITHER A TWR OR HELI TFC. THERE WAS NO RPTED TFC ON THE UNICOM FREQ, AND CHERRY POINT APCH CTL DID NOT SEE ANY EITHER. I COULD HAVE CONTACTED CHERRY POINT APCH FIRST PRIOR TO TURNING, HOWEVER, OUR XING OF FLT PATHS APPEARED IMMINENT. I FELT THE PRUDENT THING TO DO WAS SIMPLY TURN IN THE PATTERN AND DEPART OVERHEAD OF THE ARPT. THE WX WAS GOOD VFR AT THE TIME.
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.