FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04FA187 · Piper PA-28RT-201T

13 Apr 2004 · Concord, CA, United States

Piper PA-28RT-201T · Accident: partial loss of engine power (mechanical failure) during initial climb

From Buchanan Field (CCR) to Grand Junction Regional Airport (GJT)

Report a problem

Event

NTSB case
LAX04FA187
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
Unknown
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
General aviation
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-28RT-201T

Aircraft type
Piper PA-28
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
N2920C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Buchanan Field (CCR), Concord, CATo Grand Junction Regional Airport (GJT), Grand Junction, CO
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 91: General Aviation
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
Initial climb
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
Partial 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
Destroyed

Cause areas

  • Company maintenance personnel › Maintenance, improper
  • Company maintenance personnel › Maintenance, installation, incorrect
  • Engine assembly, piston › Foreign object damage
  • Exhaust system, turbocharger › Foreign object damage
  • Ignition system, spark plug › Foreign object damage

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Following a loss of engine power in the takeoff initial climb, the airplane collided with vehicles during a forced landing on a freeway. During a cross-country flight the engine began to run rough and the pilot diverted to Concord. He phoned the FBO he rented the airplane from and advised them of the problem. The company contacted another maintenance facility at Concord who found a broken exhaust valve in the number 2 cylinder. The Concord maintenance facility estimated the repair job at 20 labor hours and the rental company declined to use them. The company dispatched a mechanic to Concord to make the repairs. The company mechanic replaced the number 2 cylinder and piston; however, he replaced the correct low compression piston with an incorrect high compression piston. He performed the work in just 3 hours. He failed to conduct a complete inspection of the engine for the missing pieces of the exhaust valve. After the mechanic verbally told the pilot the airplane was "good to go," the pilot fueled the airplane to capacity and completed the engine run up with no noted abnormalities. He departed using runway 19L, the shortest runway at CCR. When the airplane was about 150 to 200 feet above ground level, the pilot noted a loss of engine power. He decided he could not return to the airport and elected to land on the I-680 freeway. During the landing, the airplane collided with vehicles and came to rest in the center divider of the freeway. The airplane was largely consumed by the post impact fire. During the post accident engine examination, various determinations were made, including the following: Cylinders 2, 4, and 6 were mechanically damaged by a foreign object, most likely the number 2 exhaust valve head; the number 4 cylinder contained a foreign object that appeared to be a portion of the number 2 valve head; the spark plugs in cylinders 2, 4, and 6 were mechanically damaged with the electrode gaps closed or nearly so; cylinders number 1, 2, 4, 5, and 6 contained improper pistons that were certified to be installed into IO-360 series engines not into the accident engine a TSIO-360-FB; and the turbocharger turbine wheel exhibited foreign object damage. The number 2 main bearing was rotated 90 degrees. The bearing rotation and fretting damage to the number 2 and 3 upper main bearing support and the numbers 6 through 11 backbone bolt locations indicate that the through bolts were inadequately torqued during the installation of the number 2 cylinder.

Probable cause

a loss of engine power due to improper maintenance repair procedures and use of improper parts.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04FA187
Event ID
20040503X00545
Case number
LAX04FA187
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, coordinates. 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: bef9fa93dd0e3c172d21430dc3acba34bb9b66a2b666489b898239249c58da2d; retrieved 2026-09-21T09:18:22.557Z.