37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 771255 |
Time | |
Date | 200801 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | intersection : fedit |
State Reference | MD |
Altitude | msl single value : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : zzz.tower |
Operator | general aviation : instructional |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | landing : missed approach |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | instruction : instructor |
Qualification | pilot : instrument pilot : cfi pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 170 flight time total : 5000 flight time type : 20 |
ASRS Report | 771255 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : far |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Chart Or Publication Flight Crew Human Performance Airspace Structure |
Primary Problem | Chart Or Publication |
Situations | |
Chart | approach : fdk rnav z rwy 23 |
Narrative:
We flew RNAV GPS Z runway 23 approach to fdk. This approach was selected in order to utilize the waas capabilities of this G1000 waas equipped cessna 182. The approach was flown normally monitoring frederick CTAF and terminated with a planned missed approach at waas minimums (690 ft). Our plan was to fly the published missed approach; which took us back to westminster (EMI) and then fly an ILS runway 23 at fdk. Following this we flew the VOR a approach into mrb and then returned. The airspace violation apparently happened during the published missed approach from the GPS approach to runway 23 at fdk. The missed approach instructions are to climb to 3000 ft direct to biyas and via 139 track to fedit and the 059 track to EMI. We followed the published missed approach instructions precisely; not realizing that the turn to fedit may encroach on the edge of the dc ADIZ. Upon landing we were asked to call potomac and were told that our flight path appeared to enter the edge of the ADIZ during our lead turn north of fedit back to EMI. There is no distance to biyas or fedit; and no depiction of the ADIZ on the approach plate; such as that located on the westminster; md approach charts. These intxns are also not depicted on the low altitude chart; so it is virtually impossible to determine their position. Knowing that the missed approach took us back to EMI we assumed that we would be well clear of the ADIZ. This assumption was apparently incorrect. This was a completely inadvertent and unintentional error on our part and I take full responsibility as the cfii on board. I conduct daily instructional flts in the vicinity and am intimately familiar with the washington dc ADIZ procedures. We were very careful to plan our exit and entry out of fdk in order to comply with the procedures and believed that the published missed approach on the GPS Z approach would keep us clear of the ADIZ. In the spirit of improving aircraft safety and identifying deficiencies and discrepancies in the national aviation system; I believe that the published GPS Z runway 23 missed approach should be modified to avoid future potential conflicts with the ADIZ. At a minimum some mention of the ADIZ should be added to this approach chart; similar to what is noted on the approach charts at westminster; md (EMI).callback conversation with reporter revealed the following information: the reporter stated that he has flown and instructed extensively in the washington dc area. The ADIZ was recently modified; and its location is depicted on approach charts for some of the surrounding airports. Such is not the case for the RNAV Z runway 23 approach for fdk. 'Fedit' is approximately 1/4 mi to the north of the ADIZ. The reporter was monitoring CTAF for fdk and the missed approach was flown utilizing the waas (wide area augmentation system) aboard the aircraft. This equipment leads the turn approaching a fix; and in this instance; led the turn at fedit by one mile. The phone call from ATC informed the reporter that the ADIZ had been penetrated by approximately 2 mi. The reporter disputes this claim.
Original NASA ASRS Text
Title: C182 INSTRUCTOR PLT IS ACCUSED OF PENETRATING DC ADIZ WHILE EXECUTING THE MISSED APCH FROM FDK.
Narrative: WE FLEW RNAV GPS Z RWY 23 APCH TO FDK. THIS APCH WAS SELECTED IN ORDER TO UTILIZE THE WAAS CAPABILITIES OF THIS G1000 WAAS EQUIPPED CESSNA 182. THE APCH WAS FLOWN NORMALLY MONITORING FREDERICK CTAF AND TERMINATED WITH A PLANNED MISSED APCH AT WAAS MINIMUMS (690 FT). OUR PLAN WAS TO FLY THE PUBLISHED MISSED APCH; WHICH TOOK US BACK TO WESTMINSTER (EMI) AND THEN FLY AN ILS RWY 23 AT FDK. FOLLOWING THIS WE FLEW THE VOR A APCH INTO MRB AND THEN RETURNED. THE AIRSPACE VIOLATION APPARENTLY HAPPENED DURING THE PUBLISHED MISSED APCH FROM THE GPS APCH TO RWY 23 AT FDK. THE MISSED APCH INSTRUCTIONS ARE TO CLB TO 3000 FT DIRECT TO BIYAS AND VIA 139 TRACK TO FEDIT AND THE 059 TRACK TO EMI. WE FOLLOWED THE PUBLISHED MISSED APCH INSTRUCTIONS PRECISELY; NOT REALIZING THAT THE TURN TO FEDIT MAY ENCROACH ON THE EDGE OF THE DC ADIZ. UPON LNDG WE WERE ASKED TO CALL POTOMAC AND WERE TOLD THAT OUR FLT PATH APPEARED TO ENTER THE EDGE OF THE ADIZ DURING OUR LEAD TURN N OF FEDIT BACK TO EMI. THERE IS NO DISTANCE TO BIYAS OR FEDIT; AND NO DEPICTION OF THE ADIZ ON THE APCH PLATE; SUCH AS THAT LOCATED ON THE WESTMINSTER; MD APCH CHARTS. THESE INTXNS ARE ALSO NOT DEPICTED ON THE LOW ALT CHART; SO IT IS VIRTUALLY IMPOSSIBLE TO DETERMINE THEIR POSITION. KNOWING THAT THE MISSED APCH TOOK US BACK TO EMI WE ASSUMED THAT WE WOULD BE WELL CLR OF THE ADIZ. THIS ASSUMPTION WAS APPARENTLY INCORRECT. THIS WAS A COMPLETELY INADVERTENT AND UNINTENTIONAL ERROR ON OUR PART AND I TAKE FULL RESPONSIBILITY AS THE CFII ON BOARD. I CONDUCT DAILY INSTRUCTIONAL FLTS IN THE VICINITY AND AM INTIMATELY FAMILIAR WITH THE WASHINGTON DC ADIZ PROCS. WE WERE VERY CAREFUL TO PLAN OUR EXIT AND ENTRY OUT OF FDK IN ORDER TO COMPLY WITH THE PROCS AND BELIEVED THAT THE PUBLISHED MISSED APCH ON THE GPS Z APCH WOULD KEEP US CLR OF THE ADIZ. IN THE SPIRIT OF IMPROVING ACFT SAFETY AND IDENTIFYING DEFICIENCIES AND DISCREPANCIES IN THE NATIONAL AVIATION SYSTEM; I BELIEVE THAT THE PUBLISHED GPS Z RWY 23 MISSED APCH SHOULD BE MODIFIED TO AVOID FUTURE POTENTIAL CONFLICTS WITH THE ADIZ. AT A MINIMUM SOME MENTION OF THE ADIZ SHOULD BE ADDED TO THIS APCH CHART; SIMILAR TO WHAT IS NOTED ON THE APCH CHARTS AT WESTMINSTER; MD (EMI).CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT HE HAS FLOWN AND INSTRUCTED EXTENSIVELY IN THE WASHINGTON DC AREA. THE ADIZ WAS RECENTLY MODIFIED; AND ITS LOCATION IS DEPICTED ON APCH CHARTS FOR SOME OF THE SURROUNDING ARPTS. SUCH IS NOT THE CASE FOR THE RNAV Z RWY 23 APCH FOR FDK. 'FEDIT' IS APPROX 1/4 MI TO THE NORTH OF THE ADIZ. THE RPTR WAS MONITORING CTAF FOR FDK AND THE MISSED APCH WAS FLOWN UTILIZING THE WAAS (WIDE AREA AUGMENTATION SYSTEM) ABOARD THE ACFT. THIS EQUIPMENT LEADS THE TURN APCHING A FIX; AND IN THIS INSTANCE; LED THE TURN AT FEDIT BY ONE MILE. THE PHONE CALL FROM ATC INFORMED THE RPTR THAT THE ADIZ HAD BEEN PENETRATED BY APPROX 2 MI. THE RPTR DISPUTES THIS CLAIM.
Data retrieved from NASA's ASRS site as of May 2009 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.