37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 988904 |
Time | |
Date | 201201 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 16000 Flight Crew Type 3000 |
Person 2 | |
Function | Captain Check Pilot Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 13000 Flight Crew Type 3000 |
Events | |
Anomaly | Deviation - Procedural Other / Unknown |
Narrative:
We were cleared by ground to push; but the push crew had some difficulty and ended up breaking the tow bar. We wrote-up the break and eventually were towed forward towards the gate; both to clear the taxiway we were blocking and for the mechanics to inspect the nose gear. Inspection complete we made sure we had the new maintenance release prior to pushback. On taxi out we also received an updated final weight manifest. All as it should be. There appeared to be some confusion about out and in times. Airborne it became apparent that someone had adjusted our original out time; closer to the time we taxied the second time. This was a surprise as we never opened a cabin door during the nose gear inspection; even though we had pulled back towards the gate. Times in the ACARS reflected such. We had a discussion via ACARS/satcom with dispatch and maintenance over an unrelated airborne write up; and brought up the discrepancy with the times. Dispatch claimed an adjustment would be made to address our concerns that pay and flight-time legality for the crew might be affected. A short time later; and likely due to that adjustment; or maybe the airborne write up; we started getting multiple messages over ACARS claiming our current release was invalid for takeoff. Further discussions had dispatch first agree with this assessment; but upon further investigation realize that we did in fact have the proper paperwork for departure. I'll wager that the discrepancy between the manually adjusted out/in times and what the plane was thinking (never blocked in) precipitated this issue. Dispatch claimed it might be due to a glitch in the maintenance computer.
Original NASA ASRS Text
Title: B767 flight crew experiences a tow bar break during push back and is pulled back to the gate for maintenance inspection. The Out time is manually adjusted; which produces a discrepancy in the release document and a great deal of message traffic once airborne.
Narrative: We were cleared by Ground to push; but the push crew had some difficulty and ended up breaking the tow bar. We wrote-up the break and eventually were towed forward towards the gate; both to clear the taxiway we were blocking and for the mechanics to inspect the nose gear. Inspection complete we made sure we had the new Maintenance release prior to pushback. On taxi out we also received an updated final weight manifest. All as it should be. There appeared to be some confusion about out and in times. Airborne it became apparent that someone had adjusted our original out time; closer to the time we taxied the second time. This was a surprise as we never opened a cabin door during the nose gear inspection; even though we had pulled back towards the gate. Times in the ACARS reflected such. We had a discussion via ACARS/SATCOM with Dispatch and Maintenance over an unrelated airborne write up; and brought up the discrepancy with the times. Dispatch claimed an adjustment would be made to address our concerns that pay and Flight-Time legality for the crew might be affected. A short time later; and likely due to that adjustment; or maybe the airborne write up; we started getting multiple messages over ACARS claiming our current Release was invalid for takeoff. Further discussions had Dispatch first agree with this assessment; but upon further investigation realize that we did in fact have the proper paperwork for departure. I'll wager that the discrepancy between the manually adjusted out/in times and what the plane was thinking (never blocked in) precipitated this issue. Dispatch claimed it might be due to a glitch in the maintenance computer.
Data retrieved from NASA's ASRS site as of July 2013 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.