37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 730842 |
Time | |
Date | 200703 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : sbgr.airport |
State Reference | FO |
Altitude | agl single value : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : parked ground other : post flight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
Qualification | other |
ASRS Report | 730842 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : far non adherence : company policies non adherence : published procedure other anomaly other |
Independent Detector | other other : 1 |
Resolutory Action | flight crew : overcame equipment problem other |
Consequence | other |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Company |
Narrative:
This flight did not automatically report its on/in time. I tried making several calls to gru operations and also sent datalink messages to gruoo; grudd; and grucsua and to find out if in fact the aircraft had landed safely. 50 mins after the flight was scheduled to land; I was unable to contact anyone -- even the gru tower. I had enlisted the help of opb as well. There were a few factors for this problem. There was no one available at gru for dispatch to contact while flts were operating into gru. Many of the numbers in the airport database I dialed either ended with a quick busy signal or just connected me to an operator. I finally got hold of someone (on operations cell who was actually in the united states) who contacted someone who then called me back. I can't find the far for reference; (NTSB 830); but an emergency should have been declared for this flight. Please insure that dispatch has a single source 24-hour contact number for its operations. If we have unscheduled; late operating; or irregular flts operating we need some one at each of our stations to call us with a contact number if the regular operations number is not going to be monitored.
Original NASA ASRS Text
Title: DISPATCHER REPORTS B767-300 ARRIVAL AT SBGR FAILED TO REPORT ARRIVAL TIMES. NUMEROUS ATTEMPTS TO CONTACT APPROPRIATE AGENCIES WERE UNSUCCESSFUL FOR AN EXTENDED PERIOD. FEELS SINGLE POINT CONTACT INFORMATION FROM OUTLYING STATIONS TO/FROM DISPATCH SHOULD BE REQUIRED FOR LATE/DELAYED FLTS.
Narrative: THIS FLT DID NOT AUTOMATICALLY RPT ITS ON/IN TIME. I TRIED MAKING SEVERAL CALLS TO GRU OPS AND ALSO SENT DATALINK MESSAGES TO GRUOO; GRUDD; AND GRUCSUA AND TO FIND OUT IF IN FACT THE ACFT HAD LANDED SAFELY. 50 MINS AFTER THE FLT WAS SCHEDULED TO LAND; I WAS UNABLE TO CONTACT ANYONE -- EVEN THE GRU TWR. I HAD ENLISTED THE HELP OF OPB AS WELL. THERE WERE A FEW FACTORS FOR THIS PROB. THERE WAS NO ONE AVAILABLE AT GRU FOR DISPATCH TO CONTACT WHILE FLTS WERE OPERATING INTO GRU. MANY OF THE NUMBERS IN THE ARPT DATABASE I DIALED EITHER ENDED WITH A QUICK BUSY SIGNAL OR JUST CONNECTED ME TO AN OPERATOR. I FINALLY GOT HOLD OF SOMEONE (ON OPS CELL WHO WAS ACTUALLY IN THE UNITED STATES) WHO CONTACTED SOMEONE WHO THEN CALLED ME BACK. I CAN'T FIND THE FAR FOR REF; (NTSB 830); BUT AN EMER SHOULD HAVE BEEN DECLARED FOR THIS FLT. PLEASE INSURE THAT DISPATCH HAS A SINGLE SOURCE 24-HR CONTACT NUMBER FOR ITS OPS. IF WE HAVE UNSCHEDULED; LATE OPERATING; OR IRREGULAR FLTS OPERATING WE NEED SOME ONE AT EACH OF OUR STATIONS TO CALL US WITH A CONTACT NUMBER IF THE REGULAR OPS NUMBER IS NOT GOING TO BE MONITORED.
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.