37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1316755 |
Time | |
Date | 201510 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | FME.Airport |
State Reference | MD |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Transponder |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Private Flight Crew Instrument |
Person 2 | |
Function | Pilot Not Flying Instructor |
Qualification | Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 35000 Flight Crew Type 25 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
I hired a cfii instructor for a series of short IFR training trips along the east coast for a period of about 2 weeks when this incident occurred. We departed with the destination of tipton; md (fme). The flight plan was IFR and we proceeded uneventfully on vectors towards the destination. At approximately 3-5 miles from the field we were asked by ATC if we had the field in site as VFR conditions prevailed. We replied affirmatively at which time ATC asked if we would like to cancel IFR. We responded 'affirmative' and ATC replied 'IFR cancelled; squawk 1200; frequency change approved.' we complied fully with those ATC instructions; by switching frequencies and squawking 1200.upon landing; we were requested by FBO personnel to call a number. I returned the call and was asked why I had squawked 1200 on final. I replied that we were complying with directives from ATC during the short final approach.since then; I have come to find out that VFR flights in and around washington; dc have special VFR flight rules of which I was unaware of at the time as I had no intention of flying VFR in this airspace with my IFR instructor. Additionally; the required training for VFR pilots in this airspace does not apply to IFR pilots and IFR flights. Therefore; when we squawked 1200 as requested by ATC on a customary short final approach in VFR conditions into a non-towered airport; we had no knowledge that we were squawking 1200 in error. I also would add that obviously ATC knew who we were and that we had changed our transponder code to 1200 VFR as we were immediately approached by the FBO with 2 telephone #s to call and make my report. I also would like to add that apparently & obviously we were the only ones squawking 1200 VFR as no one else would be doing so since we have come to find out this is not allowed in that airspace. So; the only thing we might be guilty of is changing our transponder code to something other than what we had previously been assigned. I reported all of this to the 2 stations I talked with.
Original NASA ASRS Text
Title: A general aviation pilot and flight instructor reported changing the aircraft transponder code as requested by ATC only to find that the rules in the Washington D.C. SFRA precluded this action.
Narrative: I hired a CFII instructor for a series of short IFR training trips along the east coast for a period of about 2 weeks when this incident occurred. We departed with the destination of Tipton; MD (FME). The flight plan was IFR and we proceeded uneventfully on vectors towards the destination. At approximately 3-5 miles from the field we were asked by ATC if we had the field in site as VFR conditions prevailed. We replied affirmatively at which time ATC asked if we would like to cancel IFR. We responded 'affirmative' and ATC replied 'IFR cancelled; squawk 1200; frequency change approved.' We complied fully with those ATC instructions; by switching frequencies and squawking 1200.Upon landing; we were requested by FBO personnel to call a number. I returned the call and was asked why I had squawked 1200 on final. I replied that we were complying with directives from ATC during the short final approach.Since then; I have come to find out that VFR flights in and around Washington; DC have special VFR flight rules of which I was unaware of at the time as I had no intention of flying VFR in this airspace with my IFR instructor. Additionally; the required training for VFR pilots in this airspace does not apply to IFR pilots and IFR flights. Therefore; when we squawked 1200 as requested by ATC on a customary short final approach in VFR conditions into a non-towered airport; we had no knowledge that we were squawking 1200 in error. I also would add that obviously ATC knew who we were and that we had changed our transponder code to 1200 VFR as we were immediately approached by the FBO with 2 telephone #s to call and make my report. I also would like to add that apparently & obviously we were the only ones squawking 1200 VFR as no one else would be doing so since we have come to find out this is not allowed in that airspace. So; the only thing we might be guilty of is changing our transponder code to something other than what we had previously been assigned. I reported all of this to the 2 stations I talked with.
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.