 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
First officer reports departing on an ETOPS flight using release 1 with amended takeoff weights; to discover enroute that the amended weights were for release 2. Fortunately the route had not changed.
| Attributes | |
| ACN | 1010281 |
| Time | |
| Date | 201205 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Experience | Flight Crew Last 90 Days 100 Flight Crew Total 11000 Flight Crew Type 6000 |
| Events | |
| Anomaly | Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Wrong dispatch release; arrived in operations about 1 hour 10 minutes before departure and company flight plan (release 1) had already been printed by station personnel. After review; the captain called the dispatcher to clarify his dispatch remarks about optimum altitudes en route. While the captain was signing and printing the release; I stepped to the aircraft to start the exterior inspection. Cockpit setup was not rushed. During push-back we received final weights which didn't quite make sense. Tow had increased from rel 1; but the line tow change indicated minus 1;900 pounds. We dismissed the minus as an error by load planning; thinking it should be a plus. We got new takeoff data for the final takeoff weight and completed our departure. Later in the flight; we realized load planning had not made an error; there was a release 2 for zero fuel weight increase. The final weights reflected 1;900 pounds less than release 2. In hindsight; the captain probably signed release 2; but both our copies of the flight plan were release 1. Route verification procedures were accomplished with release 1 without us realizing it was not current. Departure time was [after midnight] domicile time. Circadian cycle/fatigue was possibly a factor.
Original NASA ASRS Text
Title: First Officer reports departing on an ETOPS flight using Release 1 with amended takeoff weights; to discover enroute that the amended weights were for Release 2. Fortunately the route had not changed.
Narrative: Wrong Dispatch Release; arrived in operations about 1 hour 10 minutes before departure and Company flight plan (release 1) had already been printed by station personnel. After review; the Captain called the Dispatcher to clarify his dispatch remarks about optimum altitudes en route. While the Captain was signing and printing the release; I stepped to the aircraft to start the exterior inspection. Cockpit setup was not rushed. During push-back we received final weights which didn't quite make sense. TOW had increased from Rel 1; but the line TOW CHANGE indicated minus 1;900 LBS. We dismissed the minus as an error by Load Planning; thinking it should be a plus. We got new takeoff data for the final takeoff weight and completed our departure. Later in the flight; we realized Load Planning had not made an error; there was a release 2 for zero fuel weight increase. The final weights reflected 1;900 LBS less than Release 2. In hindsight; the Captain probably signed release 2; but both our copies of the flight plan were release 1. Route verification procedures were accomplished with Release 1 without us realizing it was not current. Departure time was [after midnight] Domicile time. Circadian cycle/fatigue was possibly a factor.
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.