FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA03LA107 · Pippert Zenith Air CH 701

6 Jun 2003 · Rochester, WA, United States

Pippert Zenith Air CH 701 · Accident: loss of engine power en route

From Skyraider Skyranch Airport (20WA) to Cricket Field (4WA2)

Report a problem

Event

NTSB case
SEA03LA107
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

Pippert Zenith Air CH 701

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
N2748
Operator
Unknown
Onboard fatalities
Unknown
Route
From Skyraider Skyranch Airport (20WA), Rochester, WATo Cricket Field (4WA2), LITTLE ROCK, WA
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
En route · climb to 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
Loss of engine power
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

The pilot reported that at a distance of about one mile from the departure airport and at 800 feet above ground level (AGL), the engine lost complete power. In an effort to avoid trees during the forced landing, the pilot was unable to maintain airspeed which resulted in a "hard" landing which broke the nose wheel axle bolt. Just before the aircraft stopped, the nose fork dug in and the aircraft nosed over. The pilot reported that the engine quit because a jet came loose in the carburetor.

Probable cause

Loose jet in the carburetor while on climb out resulting in a loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA03LA107
Event ID
20030624X00946
Case number
SEA03LA107
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2003-06-07.
  • API snapshot SHA-256: ebebe927fedb851af0f113a52466083503a61666489df782c5b30c93e956f37f; retrieved 2026-09-22T09:11:41.320Z.