37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1335353 |
Time | |
Date | 201602 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Citation X (C750) |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 83 Flight Crew Total 564 Flight Crew Type 400 |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Miss Distance | Horizontal 150 Vertical 50 |
Narrative:
ATC issued a vector of 010 for traffic and ATC immediately issued a traffic advisory of a citation on approach at my '3 o'clock.' I mistakenly turned to 100. A few seconds later I saw the citation coming directly at me (not at my 3 o'clock) at the same altitude less than 1 NM away. Quickly evaluated which direction the citation was flying and took an evasive descending left turn and reported to ATC 'citation in sight we are making an evasive left turn.' ATC did not respond. During my turn the citation initiated a climbing left turn and reported to ATC that they 'received a resolution warning and that was way too close' ATC asked if they were abandoning the approach but the citation decided to continue and contacted ZZZ tower. Later ATC clarified with me that he had issued 010 and I had flown a 100 heading. Fatigue was most likely a factor in the mistake; since we were 10 minutes away from the end of a 3.5 hour morning shift.
Original NASA ASRS Text
Title: A Traffic Watch pilot reported a near-mid-air-collision with a Cessna Citation after making a heading deviation likely due to fatigue.
Narrative: ATC issued a vector of 010 for traffic and ATC immediately issued a traffic advisory of a Citation on approach at my '3 o'clock.' I mistakenly turned to 100. A few seconds later I saw the Citation coming directly at me (not at my 3 o'clock) at the same altitude less than 1 NM away. Quickly evaluated which direction the Citation was flying and took an evasive descending left turn and reported to ATC 'Citation in sight we are making an evasive left turn.' ATC did not respond. During my turn the Citation initiated a climbing left turn and reported to ATC that they 'Received a Resolution Warning and that was way too close' ATC asked if they were abandoning the approach but the Citation decided to continue and contacted ZZZ tower. Later ATC clarified with me that he had issued 010 and I had flown a 100 heading. Fatigue was most likely a factor in the mistake; since we were 10 minutes away from the end of a 3.5 hour morning shift.
Data retrieved from NASA's ASRS site 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.