 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Untimely and incorrect GPS airport entries lead to azo class D airspace violation by a cirrus SR20 pilot.
| Attributes | |
| ACN | 515350 |
| Time | |
| Date | 200106 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : azo.airport |
| State Reference | MI |
| Altitude | msl single value : 2500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | Experimental |
| Flight Phase | cruise : level |
| Flight Plan | None |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : commercial pilot : multi engine pilot : instrument |
| Experience | flight time last 90 days : 120 flight time total : 600 flight time type : 20 |
| ASRS Report | 515350 |
| Events | |
| Anomaly | airspace violation : entry inflight encounter : weather non adherence : far non adherence : published procedure other anomaly other |
| Resolutory Action | none taken : insufficient time |
| Supplementary | |
| Problem Areas | Weather Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I was en route to pontiac, mi. The route of flight took us over the kalamazoo/battlecreek area. GPS navigation was being used with azo in the #2 GPS. Ptk was in #1 GPS. At approximately 50 mi west of azo, I referenced the sectional for airport information. Seeing the btl class D approximately 15 mi beyond azo, I programmed btl into GPS #1. This action of programming the #1 GPS automatically cross-fills into the #2 GPS. At this time, my #2 GPS now displayed distance from btl, not azo. I did not notice this change. As I continued closer to azo, I made a radio call 20 mi west of btl (thinking it was azo.) this position was actually 5 mi west of azo. By the time ATC had positively idented my position, my aircraft was 2 mi northwest of azo. This misinterp of btl with azo led to the encroachment of my aircraft into the azo class D prior to radio communications.
Original NASA ASRS Text
Title: UNTIMELY AND INCORRECT GPS ARPT ENTRIES LEAD TO AZO CLASS D AIRSPACE VIOLATION BY A CIRRUS SR20 PLT.
Narrative: I WAS ENRTE TO PONTIAC, MI. THE RTE OF FLT TOOK US OVER THE KALAMAZOO/BATTLECREEK AREA. GPS NAV WAS BEING USED WITH AZO IN THE #2 GPS. PTK WAS IN #1 GPS. AT APPROX 50 MI W OF AZO, I REFERENCED THE SECTIONAL FOR ARPT INFO. SEEING THE BTL CLASS D APPROX 15 MI BEYOND AZO, I PROGRAMMED BTL INTO GPS #1. THIS ACTION OF PROGRAMMING THE #1 GPS AUTOMATICALLY CROSS-FILLS INTO THE #2 GPS. AT THIS TIME, MY #2 GPS NOW DISPLAYED DISTANCE FROM BTL, NOT AZO. I DID NOT NOTICE THIS CHANGE. AS I CONTINUED CLOSER TO AZO, I MADE A RADIO CALL 20 MI W OF BTL (THINKING IT WAS AZO.) THIS POS WAS ACTUALLY 5 MI W OF AZO. BY THE TIME ATC HAD POSITIVELY IDENTED MY POS, MY ACFT WAS 2 MI NW OF AZO. THIS MISINTERP OF BTL WITH AZO LED TO THE ENCROACHMENT OF MY ACFT INTO THE AZO CLASS D PRIOR TO RADIO COMS.
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.