37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 195280 |
Time | |
Date | 199111 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pie |
State Reference | FL |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | climbout : takeoff ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 5500 |
ASRS Report | 195280 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 300 flight time total : 12000 flight time type : 1500 |
ASRS Report | 195440 |
Events | |
Anomaly | incursion : runway non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were cleared for takeoff on runway 35R at pie. We mistakenly lined up for and departed on runway 4. Takeoff was uneventful, but we realized our error when we noticed our departure heading was wrong. I feel the following factors contributed to this incident: 1) we were on a charter flight, operating out of an off-line airport. Because of this the airport was not in the aircraft's flight management computer data base, necessitating a change in our normal procedure of entering the takeoff runway in the computer for a visual depiction on our EFIS display. This also changed other aircraft procedures and displays, which caused a distraction to my normal habit patterns. 2) the fact that the approach ends of runway 4 and 35R are very close to one another. The lesson I have learned from this isn't a new one. No matter how technically advanced your aircraft is, never forget the basics. The old habit of checking the heading when lined up on the runway for takeoff should not be replaced by checking the fancy displays for pretty pictures. Also, when things are out of the ordinary and distrs are possible, slow down and doublechk yourself.
Original NASA ASRS Text
Title: ACR MLG WRONG RWY TKOF AT PIE.
Narrative: WE WERE CLRED FOR TKOF ON RWY 35R AT PIE. WE MISTAKENLY LINED UP FOR AND DEPARTED ON RWY 4. TKOF WAS UNEVENTFUL, BUT WE REALIZED OUR ERROR WHEN WE NOTICED OUR DEP HDG WAS WRONG. I FEEL THE FOLLOWING FACTORS CONTRIBUTED TO THIS INCIDENT: 1) WE WERE ON A CHARTER FLT, OPERATING OUT OF AN OFF-LINE ARPT. BECAUSE OF THIS THE ARPT WAS NOT IN THE ACFT'S FLT MGMNT COMPUTER DATA BASE, NECESSITATING A CHANGE IN OUR NORMAL PROC OF ENTERING THE TKOF RWY IN THE COMPUTER FOR A VISUAL DEPICTION ON OUR EFIS DISPLAY. THIS ALSO CHANGED OTHER ACFT PROCS AND DISPLAYS, WHICH CAUSED A DISTR TO MY NORMAL HABIT PATTERNS. 2) THE FACT THAT THE APCH ENDS OF RWY 4 AND 35R ARE VERY CLOSE TO ONE ANOTHER. THE LESSON I HAVE LEARNED FROM THIS ISN'T A NEW ONE. NO MATTER HOW TECHNICALLY ADVANCED YOUR ACFT IS, NEVER FORGET THE BASICS. THE OLD HABIT OF CHKING THE HDG WHEN LINED UP ON THE RWY FOR TKOF SHOULD NOT BE REPLACED BY CHKING THE FANCY DISPLAYS FOR PRETTY PICTURES. ALSO, WHEN THINGS ARE OUT OF THE ORDINARY AND DISTRS ARE POSSIBLE, SLOW DOWN AND DOUBLECHK YOURSELF.
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.