37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1372759 |
Time | |
Date | 201607 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | Pilot Not Flying First Officer |
Experience | Flight Crew Last 90 Days 197 Flight Crew Type 3000 |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 172 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown |
Narrative:
Preflight briefing; planning and checklists performed per policy and guidelines. Preflight paperwork included weather package guidance on runway 24L/6R construction which included several changes to the performance computer based on 'phase X' or 'phase X' construction and applicable 'performance computer cycle' notes. Flight was planned for 24L takeoff with thrust reduction for '24L phase X' takeoff. On taxi out to 24L; we were directed by tower for a 24L 'V' intersection takeoff. We complied with the directive and the captain recommended we perform a full thrust takeoff for 24L. Takeoff and climbout were uneventful. After takeoff and at level off; we investigated the '24L phase X' distances and concluded that the planned takeoff distance was in excess of the 24L 'V' intersection takeoff distance; thereby not allowing for a 24L 'V' or 'E7' intersection departure. Several actions should be accomplished prior to preventing this in the future. 1. Weather package should succinctly state which potential intersections are not available for departure under the current 'performance computer cycle'. Cycle XXXX only indicated that intersection E8 was not available for use during cycle XXXX. Although the performance computer requires that the pilot review the applicable date range for the current cycle; it does not allow updating of new cycles that may be within the current date range and overlap a previous cycle.2. Prior to departure from lax; the performance computer should be updated to the current cycle. Our performance computer was out of date.3. The performance computer is a (company) specific performance module. All major airlines rely on a single source performance module that relay current performance data to the specific aircraft via ACARS and printer that allow for a coordinated and updated performance module across all fleets. (Company) should adopt current minimum industry standards as related to weight; balance and performance distribution throughout the fleet.4. (Company) procedure should be updated to not only check current date range for a particular performance computer cycle; but should also allow for pilot adoption/change of new cycle. 5. (Company) should require that any aircraft operating out of a dynamic construction environment to have performance computer updated prior to aircraft participating in that environment.6. Crew operating out of dynamic construction environment should ensure that both performance computer date and 'cycle' conform to current conditions.
Original NASA ASRS Text
Title: A flight crew departed LAX Runway 24L at Taxiway V with an outdated performance computer. They discovered after takeoff their computer was not updated and that only full length takeoffs were permitted.
Narrative: Preflight briefing; planning and checklists performed per policy and guidelines. Preflight paperwork included weather package guidance on Runway 24L/6R construction which included several changes to the performance computer based on 'Phase X' or 'Phase X' construction and applicable 'Performance Computer Cycle' Notes. Flight was planned for 24L takeoff with thrust reduction for '24L Phase X' takeoff. On taxi out to 24L; we were directed by Tower for a 24L 'V' intersection takeoff. We complied with the directive and the Captain recommended we perform a full thrust takeoff for 24L. Takeoff and climbout were uneventful. After takeoff and at level off; we investigated the '24L Phase X' distances and concluded that the planned takeoff distance was in excess of the 24L 'V' intersection takeoff distance; thereby not allowing for a 24L 'V' or 'E7' intersection departure. Several actions should be accomplished prior to preventing this in the future. 1. Weather package should succinctly state which potential intersections are not available for departure under the current 'Performance Computer Cycle'. Cycle XXXX only indicated that intersection E8 was not available for use during Cycle XXXX. Although the performance computer requires that the pilot review the applicable date range for the current cycle; it does not allow updating of new cycles that may be within the current date range and overlap a previous cycle.2. Prior to departure from LAX; the performance computer should be updated to the current Cycle. Our performance computer was out of date.3. The performance computer is a (Company) specific performance module. All major airlines rely on a single source performance module that relay current performance data to the specific aircraft via ACARS and printer that allow for a coordinated and updated performance module across all fleets. (Company) should adopt current minimum industry standards as related to weight; balance and performance distribution throughout the fleet.4. (Company) procedure should be updated to not only check current date range for a particular performance computer cycle; but should also allow for pilot adoption/change of new cycle. 5. (Company) should require that any aircraft operating out of a dynamic construction environment to have performance computer updated prior to aircraft participating in that environment.6. Crew operating out of dynamic construction environment should ensure that both performance computer date and 'cycle' conform to current conditions.
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.