37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 164366 |
Time | |
Date | 199010 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : iad |
State Reference | VA |
Altitude | msl bound lower : 5000 msl bound upper : 6500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : iad |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | climbout : intermediate altitude |
Flight Plan | VFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 4 Turbojet Eng |
Flight Phase | descent : approach descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : student |
Experience | flight time last 90 days : 55 flight time total : 70 flight time type : 20 |
ASRS Report | 164366 |
Person 2 | |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp pilot : commercial |
Events | |
Anomaly | conflict : airborne less severe |
Independent Detector | other controllera other other : unspecified cockpit |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Miss Distance | horizontal : 7500 vertical : 500 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
The aircraft I was plting was climbing through 5000' MSL to 6500' MSL as part of filed VFR flight plan for a solo x-country training flight (fdk-lyh-fdk). My aircraft was approximately 3 mi north of the potomac river on the fdk 216 right. After departure from fdk and leaving the traffic pattern, I had contacted leesbury FSS to activate the filed flight plan, and then dulles approach. Though the intended route of flight did not enter the dulles arsa, I felt it would be prudent to establish radio communications with dulles approach for following, traffic advisories and sep. Dulles was using runway 19 for arriving traffic. After changing to the approach frequency, I heard a conversation between approach and an arriving air carrier X airliner. To the best of my knowledge, there were no traffic advisories issued by approach to air carrier X. Air carrier X was then handed off to the tower frequency. I then established radio contact with approach, was assigned a discrete transponder code, and advised approach of my intended route of flight. As I remember, approach then asked me to switch to a different frequency. I complied, and established radio communications with dulles approach on the new frequency. At this point, I saw air carrier X mi away, same altitude, on a diverging flight path. Approach then acknowledged my transmission, advised me of the nearby aircraft and rebuked me for being in the approach path at 5000'. I advised approach that I had the aircraft in sight, apologized for the potential conflict, and asked approach if there were either an altitude or route of flight which they would prefer me to use. I was advised to continue my climb, and was given vectors well clear of the arsa. To the best of my knowledge, at no time during this incident did I enter the arsa. The remainder of the flight and the return continued west/O incident.
Original NASA ASRS Text
Title: PLT IN SMA HAD CONFLICT WITH WDB APCHING IAD FROM NORTH.
Narrative: THE ACFT I WAS PLTING WAS CLBING THROUGH 5000' MSL TO 6500' MSL AS PART OF FILED VFR FLT PLAN FOR A SOLO X-COUNTRY TRNING FLT (FDK-LYH-FDK). MY ACFT WAS APPROX 3 MI N OF THE POTOMAC RIVER ON THE FDK 216 R. AFTER DEP FROM FDK AND LEAVING THE TFC PATTERN, I HAD CONTACTED LEESBURY FSS TO ACTIVATE THE FILED FLT PLAN, AND THEN DULLES APCH. THOUGH THE INTENDED RTE OF FLT DID NOT ENTER THE DULLES ARSA, I FELT IT WOULD BE PRUDENT TO ESTABLISH RADIO COMS WITH DULLES APCH FOR FOLLOWING, TFC ADVISORIES AND SEP. DULLES WAS USING RWY 19 FOR ARRIVING TFC. AFTER CHANGING TO THE APCH FREQ, I HEARD A CONVERSATION BTWN APCH AND AN ARRIVING ACR X AIRLINER. TO THE BEST OF MY KNOWLEDGE, THERE WERE NO TFC ADVISORIES ISSUED BY APCH TO ACR X. ACR X WAS THEN HANDED OFF TO THE TWR FREQ. I THEN ESTABLISHED RADIO CONTACT WITH APCH, WAS ASSIGNED A DISCRETE XPONDER CODE, AND ADVISED APCH OF MY INTENDED RTE OF FLT. AS I REMEMBER, APCH THEN ASKED ME TO SWITCH TO A DIFFERENT FREQ. I COMPLIED, AND ESTABLISHED RADIO COMS WITH DULLES APCH ON THE NEW FREQ. AT THIS POINT, I SAW ACR X MI AWAY, SAME ALT, ON A DIVERGING FLT PATH. APCH THEN ACKNOWLEDGED MY XMISSION, ADVISED ME OF THE NEARBY ACFT AND REBUKED ME FOR BEING IN THE APCH PATH AT 5000'. I ADVISED APCH THAT I HAD THE ACFT IN SIGHT, APOLOGIZED FOR THE POTENTIAL CONFLICT, AND ASKED APCH IF THERE WERE EITHER AN ALT OR RTE OF FLT WHICH THEY WOULD PREFER ME TO USE. I WAS ADVISED TO CONTINUE MY CLB, AND WAS GIVEN VECTORS WELL CLR OF THE ARSA. TO THE BEST OF MY KNOWLEDGE, AT NO TIME DURING THIS INCIDENT DID I ENTER THE ARSA. THE REMAINDER OF THE FLT AND THE RETURN CONTINUED W/O INCIDENT.
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.