37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 722472 |
Time | |
Date | 200701 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : msp.airport |
State Reference | MN |
Environment | |
Flight Conditions | VMC |
Person 1 | |
Affiliation | Other |
Function | other personnel other |
ASRS Report | 722472 |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable |
Supplementary | |
Problem Areas | Chart Or Publication Airport |
Primary Problem | Chart Or Publication |
Situations | |
Airport | procedure or policy : msp.airport |
Chart | airport : msp.airport |
Narrative:
While doing some research on emas for runway 12L; I discovered that msp uses a 'declared' distance on runway 12L in order to have appropriate overrun to eliminate the requirement for an emas. The declared distance is 7620 ft. The FAA AFD; commercial chart 10-9; apg; and other publications show the distance for runway 12L as 8200 ft. That would mean that pilots and dispatchers are using take-off performance data 600 ft more than what they actually have. This eliminates any safety margin. This runway has had overruns in the past. I am wondering if the FAA would find a pilot at fault for using FAA published information.callback conversation with reporter revealed the following information: the reporter stated that at least one air carrier has used the tora data instead of the asda. The reporter feels this misapplication puts the flight crews at risk of an overrun event without emas available should a reject be required using the 8200 ft full runway available. The reporter's intention with this report is to make airport users aware of possible data misuse.
Original NASA ASRS Text
Title: A RPTR CAUTIONS THAT MSP RWY 21L TAKEOFF RUN AVAILABLE LENGTH MAY BE ERRONEOUSLY USED IN LIEU OF THE AVAILABLE RWY LENGTH DATA BECAUSE NO EMAS IS INSTALLED.
Narrative: WHILE DOING SOME RESEARCH ON EMAS FOR RWY 12L; I DISCOVERED THAT MSP USES A 'DECLARED' DISTANCE ON RWY 12L IN ORDER TO HAVE APPROPRIATE OVERRUN TO ELIMINATE THE REQUIREMENT FOR AN EMAS. THE DECLARED DISTANCE IS 7620 FT. THE FAA AFD; COMMERCIAL CHART 10-9; APG; AND OTHER PUBLICATIONS SHOW THE DISTANCE FOR RWY 12L AS 8200 FT. THAT WOULD MEAN THAT PILOTS AND DISPATCHERS ARE USING TAKE-OFF PERFORMANCE DATA 600 FT MORE THAN WHAT THEY ACTUALLY HAVE. THIS ELIMINATES ANY SAFETY MARGIN. THIS RWY HAS HAD OVERRUNS IN THE PAST. I AM WONDERING IF THE FAA WOULD FIND A PILOT AT FAULT FOR USING FAA PUBLISHED INFORMATION.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT AT LEAST ONE ACR HAS USED THE TORA DATA INSTEAD OF THE ASDA. THE RPTR FEELS THIS MISAPPLICATION PUTS THE FLT CREWS AT RISK OF AN OVERRUN EVENT WITHOUT EMAS AVAILABLE SHOULD A REJECT BE REQUIRED USING THE 8200 FT FULL RWY AVAILABLE. THE RPTR'S INTENTION WITH THIS RPT IS TO MAKE ARPT USERS AWARE OF POSSIBLE DATA MISUSE.
Data retrieved from NASA's ASRS site as of January 2009 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.