37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 87277 |
Time | |
Date | 198805 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : gso |
State Reference | NC |
Altitude | msl bound lower : 8000 msl bound upper : 8000 |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : gso |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | cruise other |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument |
Experience | flight time last 90 days : 21 flight time total : 291 |
ASRS Report | 87277 |
Person 2 | |
Function | flight crew : single pilot |
Qualification | pilot : instrument |
Events | |
Anomaly | conflict : nmac non adherence : required legal separation |
Independent Detector | other controllera |
Resolutory Action | none taken : insufficient time |
Consequence | Other |
Miss Distance | horizontal : 300 vertical : 50 |
Supplementary | |
Primary Problem | Ambiguous |
Air Traffic Incident | Operational Error |
Narrative:
Occurred on IFR flight from roa to sav. Clrd from roa, V103 gso, direct ctf at 8000 etc. Over greensboro I was handed off to greensboro departure on 126.6. Several minutes later, at XA15, 2 DME south of gso VOR on 193 degree radial, ATC called traffic at my 9 O'clock position. Immediately I looked left to discover a light twin at my 8:30 position approximately 50' below my altitude and approximately 300' from my aircraft closing at an angle directly at my aircraft. The twin passed immediately behind my aircraft and turned left parallel to my route of flight at my altitude. His resulting route of flight and altitude were the same as mine and now approximately 1/2 mi west of me. Upon first sighting I had called a 'near miss' to greensboro, then reported his subsequent flight as he then turned left in front of me. Gso departure then advised that the twin had had me 'in sight' and would continue ahead of me at 8000' on R193 degree. I declared that I should have been advised of his proximity earlier. Departure stated they were trying. No deliberate evasive action had been taken as the incident had occurred too quickly. Also, any incorrect evasive action might have resulted in a collision. At approximately XA25 greensboro ATC called the light twin and asked if he had had the single. He passed behind 'in sight' upon passing. No audible response was heard on 126.6. I doubt the twin had me in sight. Clearly, separation was compromised. I believe the occurrence resulted from ATC's failure to direct the twin to a safe separation from me and the twin pilot's failure to observe 'see and avoid' and required separation minimums. Solution: perhaps a review of separation minimums with gso ATC facility with respect to early advisories of traffic conflicts. Callback conversation with reporter revealed the following information: reporter did not state precisely that he wished to file an near midair collision report, and he was not met by any FAA rep at destination airport. I explained procedure for filing official near midair collision report. Aircraft Y was off gso airport and reporter pretty sure Y was on IFR clearance at 8000'. Aircraft Y quickly pulled away from reporter aircraft X and soon was gone to another frequency. Reporter thinks ATC tried to convince him that visual sep was being applied, but reporter does not think aircraft Y pilot saw aircraft X until they almost hit.
Original NASA ASRS Text
Title: LESS THAN STANDARD SEPARATION AND NMAC BETWEEN SMALL GA AND TWIN GA ACFT. OPERATIONAL ERROR.
Narrative: OCCURRED ON IFR FLT FROM ROA TO SAV. CLRD FROM ROA, V103 GSO, DIRECT CTF AT 8000 ETC. OVER GREENSBORO I WAS HANDED OFF TO GREENSBORO DEP ON 126.6. SEVERAL MINUTES LATER, AT XA15, 2 DME S OF GSO VOR ON 193 DEG RADIAL, ATC CALLED TFC AT MY 9 O'CLOCK POSITION. IMMEDIATELY I LOOKED LEFT TO DISCOVER A LIGHT TWIN AT MY 8:30 POSITION APPROX 50' BELOW MY ALT AND APPROX 300' FROM MY ACFT CLOSING AT AN ANGLE DIRECTLY AT MY ACFT. THE TWIN PASSED IMMEDIATELY BEHIND MY ACFT AND TURNED LEFT PARALLEL TO MY ROUTE OF FLT AT MY ALT. HIS RESULTING ROUTE OF FLT AND ALT WERE THE SAME AS MINE AND NOW APPROX 1/2 MI W OF ME. UPON FIRST SIGHTING I HAD CALLED A 'NEAR MISS' TO GREENSBORO, THEN REPORTED HIS SUBSEQUENT FLT AS HE THEN TURNED LEFT IN FRONT OF ME. GSO DEP THEN ADVISED THAT THE TWIN HAD HAD ME 'IN SIGHT' AND WOULD CONTINUE AHEAD OF ME AT 8000' ON R193 DEG. I DECLARED THAT I SHOULD HAVE BEEN ADVISED OF HIS PROX EARLIER. DEP STATED THEY WERE TRYING. NO DELIBERATE EVASIVE ACTION HAD BEEN TAKEN AS THE INCIDENT HAD OCCURRED TOO QUICKLY. ALSO, ANY INCORRECT EVASIVE ACTION MIGHT HAVE RESULTED IN A COLLISION. AT APPROX XA25 GREENSBORO ATC CALLED THE LIGHT TWIN AND ASKED IF HE HAD HAD THE SINGLE. HE PASSED BEHIND 'IN SIGHT' UPON PASSING. NO AUDIBLE RESPONSE WAS HEARD ON 126.6. I DOUBT THE TWIN HAD ME IN SIGHT. CLEARLY, SEPARATION WAS COMPROMISED. I BELIEVE THE OCCURRENCE RESULTED FROM ATC'S FAILURE TO DIRECT THE TWIN TO A SAFE SEPARATION FROM ME AND THE TWIN PLT'S FAILURE TO OBSERVE 'SEE AND AVOID' AND REQUIRED SEPARATION MINIMUMS. SOLUTION: PERHAPS A REVIEW OF SEPARATION MINIMUMS WITH GSO ATC FACILITY WITH RESPECT TO EARLY ADVISORIES OF TFC CONFLICTS. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING INFORMATION: RPTR DID NOT STATE PRECISELY THAT HE WISHED TO FILE AN NMAC RPT, AND HE WAS NOT MET BY ANY FAA REP AT DEST ARPT. I EXPLAINED PROC FOR FILING OFFICIAL NMAC RPT. ACFT Y WAS OFF GSO ARPT AND RPTR PRETTY SURE Y WAS ON IFR CLRNC AT 8000'. ACFT Y QUICKLY PULLED AWAY FROM RPTR ACFT X AND SOON WAS GONE TO ANOTHER FREQ. RPTR THINKS ATC TRIED TO CONVINCE HIM THAT VISUAL SEP WAS BEING APPLIED, BUT RPTR DOES NOT THINK ACFT Y PLT SAW ACFT X UNTIL THEY ALMOST HIT.
Data retrieved from NASA's ASRS site as of August 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.