37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 387873 |
Time | |
Date | 199712 |
Day | Tue |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | airport : bna |
State Reference | TN |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : mem |
Operator | common carrier : air taxi |
Make Model Name | Baron 58/58TC |
Operating Under FAR Part | Part 135 |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 130 flight time total : 1750 flight time type : 500 |
ASRS Report | 387873 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : non radar |
Events | |
Anomaly | conflict : ground critical other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : insufficient time |
Consequence | faa : reviewed incident with flight crew other Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I taxied a baron off the end of runway 20R at bna. I chose to land on the right side, after the tower offered a sidestep to runway 20C (which I could not see). It was an uneventful landing. I didn't even use the brakes, I just let it roll out. The tower cleared us to taxi to our ramp. The first logical thing that came to mind was to take runway 31, then taxiway T6 to our ramp. I felt as if we were approaching runway 31, because I was not aware that we had already passed it. I suddenly saw unlit lights (the approach lights to runway 2L) facing the opposite direction, approaching in front of us on the runway. It was too late, due to the reduced visibility, I taxied across the light system onto the overrun. We stopped about 10 ft from where we crossed the lights. I immediately contacted the tower and told them about our situation. He contacted airport operations who brought several trucks out and took some pictures. I inspected the aircraft for damage. There was no evidence of a propeller strike or damage to the gear. Airport operations helped me push the plane back onto the runway, at which time I taxied to our ramp. I noted the occurrence in the aircraft maintenance log. A mechanic swung the gear and looked for damage which he found none. I realize that if I had the airport diagram on my lap, that this may not have happened. There was rain on the windshield and our view was extremely limited. I was so preoccupied with finding runway 31, that I must have mistaken the overrun (which has no lights facing in my direction) as the clear, blank, and empty void that one sees when approaching an intersecting runway in the dark. Tower asked me to call him on the phone. I called him and he assured me that it was no big deal and no action would be taken, but airport operations informed me that they would submit a report to our FSDO. Callback conversation with reporter revealed the following information: reporter states that he thought the aircraft was at the intersection of runway 20R and runway 31. They actually had landed and rolled to the end without realizing the mistake. He had never seen a runway with no end lights and was very surprised to be there. It was raining very heavily and the visibility was quite limited. The only damage was to 2 tires, some small nicks. He reported the incident to the chief pilot and was given some ground school training in runway lighting. To date he has heard nothing from the FAA.
Original NASA ASRS Text
Title: PLT OF BE58 BARON LNDG AT NIGHT IN POOR VISIBILITY WITH RAIN, RUNS OFF THE END OF THE RWY XING THE LIGHTS, ONTO THE OVERRUN.
Narrative: I TAXIED A BARON OFF THE END OF RWY 20R AT BNA. I CHOSE TO LAND ON THE R SIDE, AFTER THE TWR OFFERED A SIDESTEP TO RWY 20C (WHICH I COULD NOT SEE). IT WAS AN UNEVENTFUL LNDG. I DIDN'T EVEN USE THE BRAKES, I JUST LET IT ROLL OUT. THE TWR CLRED US TO TAXI TO OUR RAMP. THE FIRST LOGICAL THING THAT CAME TO MIND WAS TO TAKE RWY 31, THEN TXWY T6 TO OUR RAMP. I FELT AS IF WE WERE APCHING RWY 31, BECAUSE I WAS NOT AWARE THAT WE HAD ALREADY PASSED IT. I SUDDENLY SAW UNLIT LIGHTS (THE APCH LIGHTS TO RWY 2L) FACING THE OPPOSITE DIRECTION, APCHING IN FRONT OF US ON THE RWY. IT WAS TOO LATE, DUE TO THE REDUCED VISIBILITY, I TAXIED ACROSS THE LIGHT SYS ONTO THE OVERRUN. WE STOPPED ABOUT 10 FT FROM WHERE WE CROSSED THE LIGHTS. I IMMEDIATELY CONTACTED THE TWR AND TOLD THEM ABOUT OUR SIT. HE CONTACTED ARPT OPS WHO BROUGHT SEVERAL TRUCKS OUT AND TOOK SOME PICTURES. I INSPECTED THE ACFT FOR DAMAGE. THERE WAS NO EVIDENCE OF A PROP STRIKE OR DAMAGE TO THE GEAR. ARPT OPS HELPED ME PUSH THE PLANE BACK ONTO THE RWY, AT WHICH TIME I TAXIED TO OUR RAMP. I NOTED THE OCCURRENCE IN THE ACFT MAINT LOG. A MECH SWUNG THE GEAR AND LOOKED FOR DAMAGE WHICH HE FOUND NONE. I REALIZE THAT IF I HAD THE ARPT DIAGRAM ON MY LAP, THAT THIS MAY NOT HAVE HAPPENED. THERE WAS RAIN ON THE WINDSHIELD AND OUR VIEW WAS EXTREMELY LIMITED. I WAS SO PREOCCUPIED WITH FINDING RWY 31, THAT I MUST HAVE MISTAKEN THE OVERRUN (WHICH HAS NO LIGHTS FACING IN MY DIRECTION) AS THE CLR, BLANK, AND EMPTY VOID THAT ONE SEES WHEN APCHING AN INTERSECTING RWY IN THE DARK. TWR ASKED ME TO CALL HIM ON THE PHONE. I CALLED HIM AND HE ASSURED ME THAT IT WAS NO BIG DEAL AND NO ACTION WOULD BE TAKEN, BUT ARPT OPS INFORMED ME THAT THEY WOULD SUBMIT A RPT TO OUR FSDO. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THAT HE THOUGHT THE ACFT WAS AT THE INTXN OF RWY 20R AND RWY 31. THEY ACTUALLY HAD LANDED AND ROLLED TO THE END WITHOUT REALIZING THE MISTAKE. HE HAD NEVER SEEN A RWY WITH NO END LIGHTS AND WAS VERY SURPRISED TO BE THERE. IT WAS RAINING VERY HEAVILY AND THE VISIBILITY WAS QUITE LIMITED. THE ONLY DAMAGE WAS TO 2 TIRES, SOME SMALL NICKS. HE RPTED THE INCIDENT TO THE CHIEF PLT AND WAS GIVEN SOME GND SCHOOL TRNG IN RWY LIGHTING. TO DATE HE HAS HEARD NOTHING FROM THE FAA.
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.