37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 177141 |
Time | |
Date | 199104 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : top airport : lwc |
State Reference | KS |
Altitude | agl bound lower : 200 agl bound upper : 200 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : top |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | descent : approach landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 200 flight time total : 1200 flight time type : 180 |
ASRS Report | 177141 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | non adherence : far other anomaly other other anomaly other other spatial deviation |
Independent Detector | other other : unspecified cockpit |
Resolutory Action | flight crew : became reoriented |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After cancelling the IFR flight plan and beginning a VFR approach to lawrence, ks (approximately 30 mi east of top). (I had the RNAV set for lawrence.) I followed the HSI into the airport that I had visibility contact with on a 5 mi final. I finally realized I was approaching top instead of lawrence, ks. Being unfamiliar with lawrence, I did not realize this until short final at top. I noticed the runways did not quite match the direction (180 at top vs 150 at lawrence). During the approach I was broadcasting on 123.00 CTAF for lawrence with no communication at top. Realizing where I was, I aborted the landing at top and continued the flight to lawrence with no further occurrence. The RNAV unit was inadvertently switched from en route RNAV mode to VOR mode. West/O realizing this (with lowered visibility and rain showers), this error caused the chain of events at top.
Original NASA ASRS Text
Title: REPORTER IN SMA LOOKING FOR LWC LINED FOR LNDG AT TOP. ABORTED LNDG AND CONTINUED TO LWC.
Narrative: AFTER CANCELLING THE IFR FLT PLAN AND BEGINNING A VFR APCH TO LAWRENCE, KS (APPROX 30 MI E OF TOP). (I HAD THE RNAV SET FOR LAWRENCE.) I FOLLOWED THE HSI INTO THE ARPT THAT I HAD VIS CONTACT WITH ON A 5 MI FINAL. I FINALLY REALIZED I WAS APCHING TOP INSTEAD OF LAWRENCE, KS. BEING UNFAMILIAR WITH LAWRENCE, I DID NOT REALIZE THIS UNTIL SHORT FINAL AT TOP. I NOTICED THE RWYS DID NOT QUITE MATCH THE DIRECTION (180 AT TOP VS 150 AT LAWRENCE). DURING THE APCH I WAS BROADCASTING ON 123.00 CTAF FOR LAWRENCE WITH NO COM AT TOP. REALIZING WHERE I WAS, I ABORTED THE LNDG AT TOP AND CONTINUED THE FLT TO LAWRENCE WITH NO FURTHER OCCURRENCE. THE RNAV UNIT WAS INADVERTENTLY SWITCHED FROM ENRTE RNAV MODE TO VOR MODE. W/O REALIZING THIS (WITH LOWERED VISIBILITY AND RAIN SHOWERS), THIS ERROR CAUSED THE CHAIN OF EVENTS AT TOP.
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.