 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
C185 pilot reported a near midair collision that resulted in evasive action and a clearance deviation.
| Attributes | |
| ACN | 1692235 |
| Time | |
| Date | 201910 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Skywagon 185 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 18 Flight Crew Total 970 Flight Crew Type 650 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Clearance |
| Miss Distance | Horizontal 1 Vertical 200 |
Narrative:
In the cruise mode of my IFR flight; I was vectored through the very busy ashville airspace. I attempted to check in twice; but the controller was extraordinarily busy. I was aware that at least one aircraft abandoned their approach due to another aircraft on the runway they'd been cleared to land on; and later heard this aircraft request a return for another approach; which I ended up nose to nose with. Thankfully the perfect VFR conditions allowed me to see this oncoming aircraft. I was surprised that my TCAS (garmin 345) was not showing this aircraft; but it may have been the 2 mile range I had it set on; and I'm not used to seeing large jets that close up. Only a few moments later; I got an audible alert from the garmin 345 of traffic 12 o'clock 1 mile. I don't recall what the vertical separation was. I initiated a climbing left turn as the oncoming aircraft appeared to be turning back to ashville (to their left.) before I could alert the controller that I was climbing and turning; they instructed me to climb to 9;000 ft. (I was cruising at 8;000 ft.). Shortly thereafter; they returned me to 8;000 ft.; and handed me off to atlanta.I don't fault the controller. They were overwhelmed by the traffic - and the go-around; I suspect. But I wanted to be on the record that I deviated from my clearance to avoid a potential collision.
Original NASA ASRS Text
Title: C185 pilot reported a NMAC that resulted in evasive action and a clearance deviation.
Narrative: In the cruise mode of my IFR flight; I was vectored through the very busy Ashville airspace. I attempted to check in twice; but the Controller was extraordinarily busy. I was aware that at least one aircraft abandoned their approach due to another aircraft on the runway they'd been cleared to land on; and later heard this aircraft request a return for another approach; which I ended up nose to nose with. Thankfully the perfect VFR conditions allowed me to see this oncoming aircraft. I was surprised that my TCAS (Garmin 345) was not showing this aircraft; but it may have been the 2 mile range I had it set on; and I'm not used to seeing large jets that close up. Only a few moments later; I got an audible alert from the Garmin 345 of traffic 12 o'clock 1 mile. I don't recall what the vertical separation was. I initiated a climbing left turn as the oncoming aircraft appeared to be turning back to Ashville (to their left.) Before I could alert the controller that I was climbing and turning; they instructed me to climb to 9;000 ft. (I was cruising at 8;000 ft.). Shortly thereafter; they returned me to 8;000 ft.; and handed me off to Atlanta.I don't fault the Controller. They were overwhelmed by the traffic - and the go-around; I suspect. But I wanted to be on the record that I deviated from my clearance to avoid a potential collision.
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.