37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1366186 |
Time | |
Date | 201606 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | RKSI.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | MD-11 |
Operating Under FAR Part | Part 121 |
Flight Plan | IFR |
Component | |
Aircraft Component | ACARS |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 10000 Flight Crew Type 6000 |
Person 2 | |
Function | Pilot Not Flying Relief Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 8000 Flight Crew Type 4500 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Due to extensive problems with aerodata; no weight and balance and an inoperative satcom; we were finally able to get the takeoff data that we needed. After we had blocked out and started to taxi for 15R; ramp control advised us of a runway change to 33L. We then told ramp control that we needed to hold our position. The parking brake was then set. We tried satcom again several times. Trying to avoid a return for communication problems; the international relief officer offered to call the company on his cell phone and the captain agreed. He called the company and got the necessary takeoff data to safely continue the flight. We departed uneventfully. After a few minutes at cruise altitude; the topic of use of the cell phone came up and as a crew decided to file a report because it was a violation of the fars and fom procedures.
Original NASA ASRS Text
Title: MD-11 Flight Crew reported inability to obtain revised takeoff data after a runway change due to ACARS and SATCOM outages. Eventually a personal cell phone was used to contact Dispatch for the necessary information. After takeoff the crew questioned whether a cell phone should have been used after block out.
Narrative: Due to extensive problems with AERODATA; no weight and balance and an inoperative SATCOM; we were finally able to get the takeoff data that we needed. After we had blocked out and started to taxi for 15R; ramp control advised us of a runway change to 33L. We then told ramp control that we needed to hold our position. The parking brake was then set. We tried SATCOM again several times. Trying to avoid a return for communication problems; the International Relief Officer offered to call the company on his cell phone and the captain agreed. He called the company and got the necessary takeoff data to safely continue the flight. We departed uneventfully. After a few minutes at cruise altitude; the topic of use of the cell phone came up and as a crew decided to file a report because it was a violation of the FARs and FOM procedures.
Data retrieved from NASA's ASRS site 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.