37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 527503 |
Time | |
Date | 200110 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : lns.airport |
State Reference | PA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : lns.tower |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | landing : roll landing : go around |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tower : lns.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | landing : roll |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 25 flight time total : 845 flight time type : 460 |
ASRS Report | 527503 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Events | |
Anomaly | ground encounters other incursion : runway non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Made contact with tower controller at lancaster (class D airspace, intersecting runways 8/26 and 13/31). Approximately 9 mi southeast of facility inbound, instructed by controller to report 3 mi southeast of field and expect right traffic runway 8. I reported 3 mi southeast. Controller then asked if I could modify pattern to left traffic. I replied in the affirmative. While on final to runway 8, I was instructed to go around (landing traffic ahead of me had not yet cleared runway) and make right traffic for runway 8. Received landing clearance for runway 8 on downwind. During rollout and while clearing runway, controller queried me to confirm landing runway clearance. I responded runway 8. He then informed me I had actually been cleared to land runway 13. Controller then advised me 'not to worry about it...no other traffic was effected...it happens from time-to-time as the thresholds for the runways are somewhat close together....' (see threshold proximity on diagram below.) the controller was courteous, accommodating and professional throughout the entire exchange. I believe the reason this event occurred is because all my previous instructions from ATC were in reference to runway 8. Perhaps I misheard the actual instructions as I may have been subconsciously anticipating being assigned runway 8 for landing after the go around. Overall, the event was inadvertent and not deliberate. Safety was not compromised. I hope that others may learn from my reporting via ASRS and it will prevent recurrence of events such as this. My filing demonstrates a constructive attitude that hopefully sets an example so others, if faced with a similar event, will also file so all may benefit.
Original NASA ASRS Text
Title: SMA PLT LANDED ON THE WRONG RWY AT LNS.
Narrative: MADE CONTACT WITH TWR CTLR AT LANCASTER (CLASS D AIRSPACE, INTERSECTING RWYS 8/26 AND 13/31). APPROX 9 MI SE OF FACILITY INBOUND, INSTRUCTED BY CTLR TO RPT 3 MI SE OF FIELD AND EXPECT R TFC RWY 8. I RPTED 3 MI SE. CTLR THEN ASKED IF I COULD MODIFY PATTERN TO L TFC. I REPLIED IN THE AFFIRMATIVE. WHILE ON FINAL TO RWY 8, I WAS INSTRUCTED TO GO AROUND (LNDG TFC AHEAD OF ME HAD NOT YET CLRED RWY) AND MAKE R TFC FOR RWY 8. RECEIVED LNDG CLRNC FOR RWY 8 ON DOWNWIND. DURING ROLLOUT AND WHILE CLRING RWY, CTLR QUERIED ME TO CONFIRM LNDG RWY CLRNC. I RESPONDED RWY 8. HE THEN INFORMED ME I HAD ACTUALLY BEEN CLRED TO LAND RWY 13. CTLR THEN ADVISED ME 'NOT TO WORRY ABOUT IT...NO OTHER TFC WAS EFFECTED...IT HAPPENS FROM TIME-TO-TIME AS THE THRESHOLDS FOR THE RWYS ARE SOMEWHAT CLOSE TOGETHER....' (SEE THRESHOLD PROX ON DIAGRAM BELOW.) THE CTLR WAS COURTEOUS, ACCOMMODATING AND PROFESSIONAL THROUGHOUT THE ENTIRE EXCHANGE. I BELIEVE THE REASON THIS EVENT OCCURRED IS BECAUSE ALL MY PREVIOUS INSTRUCTIONS FROM ATC WERE IN REF TO RWY 8. PERHAPS I MISHEARD THE ACTUAL INSTRUCTIONS AS I MAY HAVE BEEN SUBCONSCIOUSLY ANTICIPATING BEING ASSIGNED RWY 8 FOR LNDG AFTER THE GAR. OVERALL, THE EVENT WAS INADVERTENT AND NOT DELIBERATE. SAFETY WAS NOT COMPROMISED. I HOPE THAT OTHERS MAY LEARN FROM MY RPTING VIA ASRS AND IT WILL PREVENT RECURRENCE OF EVENTS SUCH AS THIS. MY FILING DEMONSTRATES A CONSTRUCTIVE ATTITUDE THAT HOPEFULLY SETS AN EXAMPLE SO OTHERS, IF FACED WITH A SIMILAR EVENT, WILL ALSO FILE SO ALL MAY BENEFIT.
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.