FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Bridge Piper PA-31-350 accident

23 Jul 2000 · Boulder City, NV, United States

Piper PA-31-350 · Accident: total loss of engine power (mechanical failure) en route

From 61B to Grand Canyon National Park Airport (GCN)

Report a problem

Event

NTSB case
LAX00LA277
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-31-350

Aircraft type
Piper PA-31
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N600EE
Operator
Air Bridge
Onboard fatalities
Unknown
Route
From 61BTo Grand Canyon National Park Airport (GCN), Grand Canyon, AZ
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Total loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Company maintenance personnel › Maintenance, compliance with ad, not performed
  • Company maintenance personnel › Maintenance, inspection, inadequate
  • Fuel system, line › Fatigue

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

After a complete loss of power from the left engine, the airplane was unable to maintain altitude on one engine and collided with large rocks during a landing on a beach at a recreation lake. Following a maximum gross weight takeoff, the airplane climbed to a cruise altitude of 9,500 feet msl. About 20 minutes into the flight, the pilot heard a loud "pop" sound and the left engine surged once. The pilot immediately turned around and started back toward lower terrain. He then attempted to restore power by following the checklist items, but was unsuccessful, and he then completed the shutdown and feather checklists. While proceeding to the closest airstrip for a landing, the airplane would not hold altitude at best single engine rate of climb airspeed and began to drift down. The pilot believed he would have an insufficient altitude margin to make any of the nearby landing airstrips or clear the mountainous terrain between his position and the departure airport. The pilot elected to land on the beach of a lake. During the landing rollout, the aircraft encountered moderately sized rocks and collapsed the nose and left landing gear. The left engine was installed on a test stand and examined. The only discrepancy was a fractured fuel injector line for the No. 6 cylinder injector nozzle. The fracture was completely through the line near the manifold end at a brazed joint between the line and a larger diameter ferrule end. No support clamps were observed on this line between the manifold and the injector nozzle. Support clamps were found on the injector lines to the remaining 5 cylinders. The fractured fuel injector line on the No. 6 cylinder was replaced with a serviceable line and the engine was started, accelerated to full power, and met all specifications. Metallurgical examination of the fractured fuel injector line found that it failed in fatigue from multiple origin sites on the line's outer surface. No material defects or mechanical damage, which could have contributed to the crack initiation, was found at any origin site. No evidence of clamps was found at any point along the line length. AD 93-02-05 applied to this engine and mandated compliance with Lycoming Service Bulletin 342A. The provisions of the AD and the SB require a one time inspection, then recurring inspections of the fuel injector lines at each 100-hour inspection, at each overhaul, and after any maintenance has been performed where the lines have been disconnected, moved or loosened. The line inspection involves looking for any evidence of cracks, dents, or other unserviceable wear indicators. The SB requires that any line found without clamps supporting the line run must be replaced, and that each line must be clamped. Specific clamping points for each line are noted on a diagram for each engine model incorporated within the Service Bulletin. The engine was last inspected on July 14, 2000, 23 hours prior to the accident. The fuel injection system on this engine is a constant flow type and a leak in any one line would reduce the flow to the other cylinders, which would result in an excessively lean condition. Based on both the pilot's report of the conditions at the landing site and the METAR from the closest aviation observation station, the density altitude on the surface was calculated to be 4,700 feet. The outside air temperature at the site, and the estimated temperature at the aircraft's cruise altitude, were outside of the temperature envelope for a positive rate of climb on the aircraft's single engine climb performance chart in the Airplane Flight Manual. According to Piper, the temperature lines on the charts are limits and no extrapolation can be made for points outside of the temperature lines.

Probable cause

The fatigue fracture and separation of the No. 6 cylinder fuel injector line due to the company maintenance personnel's failure to comply with an Airworthiness Directive. A factor in the accident was the company's decision to operate the aircraft in environmental conditions, which were outside of the single engine performance capability of the aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA277
Event ID
20001212X21517
Case number
LAX00LA277
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 319424c8bc48d008d1712ff4e491667a4a6b4a1182b68cbf8771caa8315f8a0c; retrieved 2026-09-18T16:31:17.660Z.