 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier dispatcher believes company reporting methods for aircraft operating under FAA operations specifications (special fuel reserve requirements) are inadequate.
| Attributes | |
| ACN | 709401 |
| Time | |
| Date | 200609 |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | other personnel |
| Events | |
| Independent Detector | other other : dispatcher |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | FAA Company |
| Primary Problem | Company |
Narrative:
Company automation procedures in reference to position reporting required for operations specifications seem to be inadequate. Alert is sent when flight has not reported a position in 90 mins. When alert is received flight may already be in non compliance with operations specifications. Alert needs to be sent before 90 mins to allow time to obtain required data. When dispatcher responsibility in this situation has been brought to the company's attention the attitude is that all the dispatcher has to do is make sure the flight gets the alert and the rest is up to the flight to relay the data. There was an automated ACARS message that was in effect for several days that would have resolved the problem if it was sent before 90 mins. That message was: attention captain; position report required over or abeam last or next check point on flight plan. FMC does not automatic-report over or abeam points manually built within the FMC. In accordance with operations specifications; position reports with time; fuel and altitude; are required at intervals not to exceed 90 mins. This message was rescinded and a new automated message has replaced it: captain; we have not received a position report with fuel for over 90 mins.
Original NASA ASRS Text
Title: ACR DISPATCHER BELIEVES COMPANY RPTING METHODS FOR ACFT OPERATING UNDER FAA OPS SPECS (SPECIAL FUEL RESERVE REQUIREMENTS) ARE INADEQUATE.
Narrative: COMPANY AUTOMATION PROCS IN REF TO POS RPTING REQUIRED FOR OPS SPECS SEEM TO BE INADEQUATE. ALERT IS SENT WHEN FLT HAS NOT RPTED A POS IN 90 MINS. WHEN ALERT IS RECEIVED FLT MAY ALREADY BE IN NON COMPLIANCE WITH OPS SPECS. ALERT NEEDS TO BE SENT BEFORE 90 MINS TO ALLOW TIME TO OBTAIN REQUIRED DATA. WHEN DISPATCHER RESPONSIBILITY IN THIS SITUATION HAS BEEN BROUGHT TO THE COMPANY'S ATTN THE ATTITUDE IS THAT ALL THE DISPATCHER HAS TO DO IS MAKE SURE THE FLT GETS THE ALERT AND THE REST IS UP TO THE FLT TO RELAY THE DATA. THERE WAS AN AUTOMATED ACARS MESSAGE THAT WAS IN EFFECT FOR SEVERAL DAYS THAT WOULD HAVE RESOLVED THE PROB IF IT WAS SENT BEFORE 90 MINS. THAT MESSAGE WAS: ATTN CAPT; POS RPT REQUIRED OVER OR ABEAM LAST OR NEXT CHK POINT ON FLT PLAN. FMC DOES NOT AUTO-RPT OVER OR ABEAM POINTS MANUALLY BUILT WITHIN THE FMC. IN ACCORDANCE WITH OPS SPECS; POS RPTS WITH TIME; FUEL AND ALT; ARE REQUIRED AT INTERVALS NOT TO EXCEED 90 MINS. THIS MESSAGE WAS RESCINDED AND A NEW AUTOMATED MESSAGE HAS REPLACED IT: CAPT; WE HAVE NOT RECEIVED A POS RPT WITH FUEL FOR OVER 90 MINS.
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.