37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 753502 |
Time | |
Date | 200709 |
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 | |
Operator | general aviation : instructional |
Make Model Name | Cessna Aircraft Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | landing : missed approach |
Flight Plan | VFR |
Aircraft 2 | |
Route In Use | approach : instrument non precision |
Person 1 | |
Affiliation | other |
Function | instruction : trainee |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 4 flight time total : 1087 flight time type : 71 |
ASRS Report | 753502 |
Person 2 | |
Affiliation | other |
Function | instruction : instructor |
Qualification | pilot : cfi pilot : commercial pilot : multi engine pilot : instrument |
Experience | flight time last 90 days : 106 flight time total : 6516 flight time type : 630 |
ASRS Report | 753702 |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Chart Or Publication Airspace Structure Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Situations | |
Chart | approach : fdk rnav z rwy 23 |
Narrative:
I was doing air work and instrument recurrency training with an instructor in preparation for an annual check ride. The purpose of the flight was to become more familiar with the apollo GX55 GPS in the aircraft; so we were concentrating on approaches using the GPS. After a VOR runway 34 approach to dmw we did an RNAV (GPS) Z runway 23 approach to fdk. While flying the published missed approach procedure and reaching fedit we turned the GPS back to the map mode and discovered that we were inside the ADIZ. We immediately turned further north and exited the ADIZ. The approach plates that I was using were current; downloaded from the pilot group members-only web site that morning. Unlike the VOR runway 34 and RNAV (GPS) runway 34 approaches to carroll county (dmw); which clearly show the ADIZ boundary; the RNAV (GPS) Z runway 23 approach to fdk doesn't show the ADIZ boundary. Mistakenly as it turns out; I assumed that the ADIZ wasn't a factor. It wasn't until later that my instructor plotted the location of fedit and discovered that the waypoint is inside the ADIZ! If we knew that ahead of time we wouldn't have picked this approach; or wouldn't have flown the published missed approach procedure. However; there is no warning or caution note on the approach plate and no mention of this in the fdc NOTAMS. It's possible that the tsa and/or charting folks believe that anyone flying the approach would be on an IFR flight plan so the ADIZ wouldn't be a factor; but this doesn't take into account all the pilots who fly practice approaches in VFR conditions without ATC assistance. We had our DME set on the dca VOR for additional situational awareness; but it is located on the far right of the cockpit and my instructor was looking to the left; explaining some of the functions of the GPS. Other factors are: 1) my instructor doesn't usually fly this approach because he has been teaching mostly in another airplane with a G-1000 glass cockpit. Its GPS has more memory; so he usually flies the RNAV (GPS) Y runway 23 approach (which has a different missed approach procedure much closer to the airport) and not available in the database of the aircraft we were using; and 2) the last time he flew the RNAV (GPS) Z runway 23 approach it was before the ADIZ change and fedit was outside the ADIZ boundary. I believe the problem could be corrected by revising the missed approach procedure and/or recharting the approach to include the ADIZ boundary.supplemental information from acn 753702: in summary; there were three contributing factors to our unintentional incursion into the ADIZ airspace. There were: 1) high workload due to the student's unfamiliarity with the GPS system which resulted in limited opportunity for me to observe the map display during the missed approach procedure. 2) my incorrect assumption that; based on the depiction of the nearby ADIZ airspace on the approach charts for the earlier VOR runway 34 approach at dmw; the same depiction of this airspace would be present on the GPS approach and subsequent missed approach into fdk; and 3) belief that absence any apparent reason to do so; that the approach designers would not unnecessarily place one or more of the approach fixes within the restr ADIZ airspace.
Original NASA ASRS Text
Title: A PLT AND INSTRUCTOR ON A FDK RNAV Z RWY 23 PRACTICE FLEW INTO THE ADIZ ON THE MISSED APCH BECAUSE OF A GPS CONFIGURATION AND NO ADIZ PLOTTED ON THE APCH PLATE.
Narrative: I WAS DOING AIR WORK AND INSTRUMENT RECURRENCY TRAINING WITH AN INSTRUCTOR IN PREPARATION FOR AN ANNUAL CHK RIDE. THE PURPOSE OF THE FLT WAS TO BECOME MORE FAMILIAR WITH THE APOLLO GX55 GPS IN THE ACFT; SO WE WERE CONCENTRATING ON APPROACHES USING THE GPS. AFTER A VOR RWY 34 APCH TO DMW WE DID AN RNAV (GPS) Z RWY 23 APCH TO FDK. WHILE FLYING THE PUBLISHED MISSED APCH PROC AND REACHING FEDIT WE TURNED THE GPS BACK TO THE MAP MODE AND DISCOVERED THAT WE WERE INSIDE THE ADIZ. WE IMMEDIATELY TURNED FURTHER N AND EXITED THE ADIZ. THE APCH PLATES THAT I WAS USING WERE CURRENT; DOWNLOADED FROM THE PLT GROUP MEMBERS-ONLY WEB SITE THAT MORNING. UNLIKE THE VOR RWY 34 AND RNAV (GPS) RWY 34 APPROACHES TO CARROLL COUNTY (DMW); WHICH CLEARLY SHOW THE ADIZ BOUNDARY; THE RNAV (GPS) Z RWY 23 APPROACH TO FDK DOESN'T SHOW THE ADIZ BOUNDARY. MISTAKENLY AS IT TURNS OUT; I ASSUMED THAT THE ADIZ WASN'T A FACTOR. IT WASN'T UNTIL LATER THAT MY INSTRUCTOR PLOTTED THE LOCATION OF FEDIT AND DISCOVERED THAT THE WAYPOINT IS INSIDE THE ADIZ! IF WE KNEW THAT AHEAD OF TIME WE WOULDN'T HAVE PICKED THIS APCH; OR WOULDN'T HAVE FLOWN THE PUBLISHED MISSED APCH PROC. HOWEVER; THERE IS NO WARNING OR CAUTION NOTE ON THE APCH PLATE AND NO MENTION OF THIS IN THE FDC NOTAMS. IT'S POSSIBLE THAT THE TSA AND/OR CHARTING FOLKS BELIEVE THAT ANYONE FLYING THE APCH WOULD BE ON AN IFR FLT PLAN SO THE ADIZ WOULDN'T BE A FACTOR; BUT THIS DOESN'T TAKE INTO ACCOUNT ALL THE PLTS WHO FLY PRACTICE APPROACHES IN VFR CONDITIONS WITHOUT ATC ASSISTANCE. WE HAD OUR DME SET ON THE DCA VOR FOR ADDITIONAL SITUATIONAL AWARENESS; BUT IT IS LOCATED ON THE FAR RIGHT OF THE COCKPIT AND MY INSTRUCTOR WAS LOOKING TO THE LEFT; EXPLAINING SOME OF THE FUNCTIONS OF THE GPS. OTHER FACTORS ARE: 1) MY INSTRUCTOR DOESN'T USUALLY FLY THIS APCH BECAUSE HE HAS BEEN TEACHING MOSTLY IN ANOTHER AIRPLANE WITH A G-1000 GLASS COCKPIT. ITS GPS HAS MORE MEMORY; SO HE USUALLY FLIES THE RNAV (GPS) Y RWY 23 APCH (WHICH HAS A DIFFERENT MISSED APCH PROC MUCH CLOSER TO THE ARPT) AND NOT AVAILABLE IN THE DATABASE OF THE ACFT WE WERE USING; AND 2) THE LAST TIME HE FLEW THE RNAV (GPS) Z RWY 23 APCH IT WAS BEFORE THE ADIZ CHANGE AND FEDIT WAS OUTSIDE THE ADIZ BOUNDARY. I BELIEVE THE PROBLEM COULD BE CORRECTED BY REVISING THE MISSED APCH PROC AND/OR RECHARTING THE APCH TO INCLUDE THE ADIZ BOUNDARY.SUPPLEMENTAL INFO FROM ACN 753702: IN SUMMARY; THERE WERE THREE CONTRIBUTING FACTORS TO OUR UNINTENTIONAL INCURSION INTO THE ADIZ AIRSPACE. THERE WERE: 1) HIGH WORKLOAD DUE TO THE STUDENT'S UNFAMILIARITY WITH THE GPS SYSTEM WHICH RESULTED IN LIMITED OPPORTUNITY FOR ME TO OBSERVE THE MAP DISPLAY DURING THE MISSED APCH PROC. 2) MY INCORRECT ASSUMPTION THAT; BASED ON THE DEPICTION OF THE NEARBY ADIZ AIRSPACE ON THE APCH CHARTS FOR THE EARLIER VOR RWY 34 APCH AT DMW; THE SAME DEPICTION OF THIS AIRSPACE WOULD BE PRESENT ON THE GPS APCH AND SUBSEQUENT MISSED APCH INTO FDK; AND 3) BELIEF THAT ABSENCE ANY APPARENT REASON TO DO SO; THAT THE APCH DESIGNERS WOULD NOT UNNECESSARILY PLACE ONE OR MORE OF THE APCH FIXES WITHIN THE RESTR ADIZ AIRSPACE.
Data retrieved from NASA's ASRS site as of January 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.