37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 387230 |
Time | |
Date | 199712 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : phx |
State Reference | AZ |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : las |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | other |
Flight Plan | None |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
Qualification | other |
ASRS Report | 387230 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : far other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
Note MEL xyz. This MEL as derived from the air carrier flight planning system does not exist in the MEL book as xyz. This MEL when placed on a flight would be a violation of FARS. What would it take to get this discrepancy taken care of? Because it was necessary to file a second in-house report, I feel it necessitates a NASA report.
Original NASA ASRS Text
Title: A DISPATCHER RPTS A BOGUS OR NONEXISTENT MEL REF IS LOADED IN THE FLT PLANNING COMPUTER WHICH UNLAWFULLY RESTRICTS THE ACFT.
Narrative: NOTE MEL XYZ. THIS MEL AS DERIVED FROM THE ACR FLT PLANNING SYS DOES NOT EXIST IN THE MEL BOOK AS XYZ. THIS MEL WHEN PLACED ON A FLT WOULD BE A VIOLATION OF FARS. WHAT WOULD IT TAKE TO GET THIS DISCREPANCY TAKEN CARE OF? BECAUSE IT WAS NECESSARY TO FILE A SECOND IN-HOUSE RPT, I FEEL IT NECESSITATES A NASA RPT.
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.