 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot neglected to switch to the advisory frequency for his intended airfield and landed the wrong way on the active runway.
| Attributes | |
| ACN | 1268528 |
| Time | |
| Date | 201506 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | BTF.Airport |
| State Reference | UT |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 50 Flight Crew Total 4700 Flight Crew Type 1200 |
| Events | |
| Anomaly | Conflict Ground Conflict Less Severe Ground Incursion Runway |
| Miss Distance | Horizontal 1500 Vertical 0 |
Narrative:
[Aircraft] was on IFR flight plan from btf. When close to btf and below the class B floor; which was 7;500 MSL; I cancelled IFR and I was supposed to switch to advisory; 122.8.I was looking for runway 34; because although I was only slightly familiar with btf; my passenger; in the right seat; was also a pilot and was very familiar with btf. He told me I could go straight in to runway 34. We were too close to btf after the tower handoff; but I got runway 34 in sight and descended to land.we did not realized that 16 was active; and when I landed; there was a piper archer who exited runway 16 to get out of my way. I should have switched to advisory and circled over the airport traffic pattern and listened to advisory and would have realized I was planning to land the wrong runway. Part of the problem was the wind was light and variable and either runway could have been active; and I also put too much faith in my passenger to know what was going on; even though neither of us realized the problem until we landed. Also; during this flight; my right seat passenger was trying to become more familiar with [the aircraft] because he was interested in purchasing one; and this distracted me from my usual procedure to set up a visual approach far ahead and have everything planned and understood in advance.
Original NASA ASRS Text
Title: A pilot neglected to switch to the Advisory Frequency for his intended airfield and landed the wrong way on the active runway.
Narrative: [Aircraft] was on IFR flight plan from BTF. When close to BTF and below the Class B floor; which was 7;500 MSL; I cancelled IFR and I was supposed to switch to Advisory; 122.8.I was looking for runway 34; because although I was only slightly familiar with BTF; my passenger; in the right seat; was also a pilot and was very familiar with BTF. He told me I could go straight in to Runway 34. We were too close to BTF after the tower handoff; but I got Runway 34 in sight and descended to land.We did not realized that 16 was active; and when I landed; there was a Piper Archer who exited runway 16 to get out of my way. I should have switched to Advisory and circled over the airport traffic pattern and listened to advisory and would have realized I was planning to land the wrong runway. Part of the problem was the wind was light and variable and either runway could have been active; and I also put too much faith in my passenger to know what was going on; even though neither of us realized the problem until we landed. Also; during this flight; my right seat passenger was trying to become more familiar with [the aircraft] because he was interested in purchasing one; and this distracted me from my usual procedure to set up a visual approach far ahead and have everything planned and understood in advance.
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.