FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA197 · Boeing A75N1(PT17) UNDESIGNAT

4 Sept 2017 · Santa Paula, CA, United States

Boeing A75N1(PT17) UNDESIGNAT · Accident en route

From Santa Paula Airport (SZP) to Santa Paula Airport (SZP)

Report a problem

Event

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

Boeing A75N1(PT17) UNDESIGNAT

Aircraft type
Boeing A75
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
N75753
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Paula Airport (SZP), Santa Paula, CATo Santa Paula Airport (SZP), Santa Paula, CA
Aircraft age
About 75 years (built 1942)
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
Defining eventThe 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
Unknown or undetermined
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

  • Not determined › Not determined

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

NTSB narrative

The commercial pilot departed on a sightseeing flight with a passenger onboard; the airplane was near its published gross weight. The pilot had experienced some difficulty starting the engine before takeoff, which he resolved after removing and reinstalling the primer several times. The takeoff roll and departure were uneventful; however, when the airplane transitioned to initial climb, its climb performance reduced, and when it reached about 500 ft mean sea level, the airplane stopped climbing, which the pilot reported that he believed was due to a partial loss of engine power. Subsequently, the pilot turned the airplane back toward the departure airport, but after realizing that it would not reach the airport, he chose to conduct an off-airport forced landing. The airplane touched down in a dry riverbed, and it impacted brush and then nosed over and came to rest inverted, which resulted in substantial damage to the upper and lower wings.

The airplane had sufficient fuel for the accident flight. Postaccident examination of the engine revealed numerous preimpact anomalies, including a leak in the engine primer line, which had developed over time due to its repetitive contact with the engine exhaust adjacent to it. The leak likely resulted in the pilot needing to add an excessive number of primer shots to start the engine before departure and led to some of his failed engine start attempts. Further, examination of the engine revealed that the cold compression on the No. 3 cylinder was low, that a spark plug was defective, that two ignition cables had significantly low insulation resistance, and that several of the forward ignition harness elbows were bent. Low compression is not an isolated incident, and it is possible that the pilot had been operating the airplane with low cold compression on the No. 3 cylinder for some time; therefore, it could not be determined if this contributed to the power loss. Although a defective spark plug could have resulted in a negligible power loss, it likely would not have prevented the airplane from climbing during the accident flight. Further, it could not be determined if the ignition harnesses were bent during the impact sequence; therefore, it could not be determined whether the condition of the ignition system contributed to the loss of engine power.

Although the atmospheric conditions at the time of the accident were conducive to the accumulation of serious icing at glide power, it could not be determined if carburetor ice had formed while the airplane was idling on the ground. The reason for the loss of engine power could not be determined.

Probable cause

A partial loss of engine power during initial climb for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA197
Event ID
20170904X92641
Case number
WPR17LA197
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 8991faeb24179a82c76453ea35e91d2c00293a5140d9161bca93269cacdc5642; retrieved 2026-09-16T05:47:10.170Z.