37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 598083 |
Time | |
Date | 200310 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : bal.vortac |
State Reference | MD |
Altitude | msl single value : 6000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : personal |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : pct.tracon |
Make Model Name | PA-44 Seminole Turbo Seminole |
Navigation In Use | other other vortac |
Flight Phase | cruise : level |
Route In Use | approach : traffic pattern enroute airway : v93.airway |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : multi engine |
Experience | flight time last 90 days : 23 flight time total : 460 flight time type : 460 |
ASRS Report | 598083 |
Events | |
Anomaly | conflict : nmac non adherence : required legal separation non adherence : published procedure |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Miss Distance | horizontal : 200 vertical : 0 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
I was on an IFR flight plan from cge to gai wbound at 6000 ft on V93 between the graco intersection and the balance VOR in VMC. I was approximately 11 mi east of the balance VOR, placing me near annapolis, md, to my left. ATC began a repeated exchange of communications with what appeared to be VFR traffic, indicating that they needed to perform a fly-by at the annapolis stadium at a specified time and at one point, asked if they could have flight following. In the course of the conversation, ATC indicated that this was in the ADIZ and a flight plan was required. ATC then began to communicate with an aircraft indicating that traffic was wbound at 6000 ft. Believing that ATC was referring to my aircraft, I began a more intense search for traffic. Almost immediately, I saw an aircraft at my 12 O'clock, same altitude, in a slight right bank that passed to my left in less than 2 seconds. Horizontal separation was approximately 200 ft. I immediately banked to my right and communicated to ATC that I had traffic in sight and that was very close. ATC then communicated to me that the traffic separation problem was his fault. ATC communicated the same message to the other aircraft. The flight continued as planned to gai. There was some concern as to the location of the VFR traffic requesting the fly-by. I believed this traffic was much lower, but its location was unknown to me. Conditions were VMC, slight haze on the horizon. Upon seeing the aircraft at my 12 O'clock position, I banked to the right though I believe there was slight horizontal separation and the other aircraft was in a slight right bank. ATC was very quick to indicate that the traffic separation problem was his fault and repeated this statement several times appearing to be apologetic.
Original NASA ASRS Text
Title: C182 EXPERIENCED NMAC DURING IFR FLT AT 6000 FT IN PCT'S AIRSPACE.
Narrative: I WAS ON AN IFR FLT PLAN FROM CGE TO GAI WBOUND AT 6000 FT ON V93 BTWN THE GRACO INTXN AND THE BAL VOR IN VMC. I WAS APPROX 11 MI E OF THE BAL VOR, PLACING ME NEAR ANNAPOLIS, MD, TO MY L. ATC BEGAN A REPEATED EXCHANGE OF COMS WITH WHAT APPEARED TO BE VFR TFC, INDICATING THAT THEY NEEDED TO PERFORM A FLY-BY AT THE ANNAPOLIS STADIUM AT A SPECIFIED TIME AND AT ONE POINT, ASKED IF THEY COULD HAVE FLT FOLLOWING. IN THE COURSE OF THE CONVERSATION, ATC INDICATED THAT THIS WAS IN THE ADIZ AND A FLT PLAN WAS REQUIRED. ATC THEN BEGAN TO COMMUNICATE WITH AN ACFT INDICATING THAT TFC WAS WBOUND AT 6000 FT. BELIEVING THAT ATC WAS REFERRING TO MY ACFT, I BEGAN A MORE INTENSE SEARCH FOR TFC. ALMOST IMMEDIATELY, I SAW AN ACFT AT MY 12 O'CLOCK, SAME ALT, IN A SLIGHT R BANK THAT PASSED TO MY L IN LESS THAN 2 SECONDS. HORIZ SEPARATION WAS APPROX 200 FT. I IMMEDIATELY BANKED TO MY R AND COMMUNICATED TO ATC THAT I HAD TFC IN SIGHT AND THAT WAS VERY CLOSE. ATC THEN COMMUNICATED TO ME THAT THE TFC SEPARATION PROB WAS HIS FAULT. ATC COMMUNICATED THE SAME MESSAGE TO THE OTHER ACFT. THE FLT CONTINUED AS PLANNED TO GAI. THERE WAS SOME CONCERN AS TO THE LOCATION OF THE VFR TFC REQUESTING THE FLY-BY. I BELIEVED THIS TFC WAS MUCH LOWER, BUT ITS LOCATION WAS UNKNOWN TO ME. CONDITIONS WERE VMC, SLIGHT HAZE ON THE HORIZON. UPON SEEING THE ACFT AT MY 12 O'CLOCK POS, I BANKED TO THE R THOUGH I BELIEVE THERE WAS SLIGHT HORIZ SEPARATION AND THE OTHER ACFT WAS IN A SLIGHT R BANK. ATC WAS VERY QUICK TO INDICATE THAT THE TFC SEPARATION PROB WAS HIS FAULT AND REPEATED THIS STATEMENT SEVERAL TIMES APPEARING TO BE APOLOGETIC.
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.