FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI98LA175 · Boeing Stearman A75-N1

27 May 1998 · West Fargo, ND, United States

Boeing Stearman A75-N1 · Accident: total loss of engine power (non-mechanical) while maneuvering

From 59Y · ARGUSVILLE, ND to 59Y · ND

Report a problem

Event

NTSB case
CHI98LA175
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
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 Stearman A75-N1

Aircraft type
Boeing Stearman 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
N49955
Operator
Unknown
Onboard fatalities
Unknown
Route
From 59Y · ARGUSVILLE, NDTo 59Y · ND
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 137: Agricultural
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
Maneuvering · aerial application
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 (non-mechanical)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Fuel exhaustion
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

  • Fluid, fuel › Exhaustion
  • Pilot in command › Fuel supply, inadequate

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

NTSB narrative

The pilot reported the engine lost power during the aerial application flight. A forced landing was made on soft terrain during which time the airplane nosed over. Inspection of the airplane revealed no indication of fuel on board. There was also no indication of fuel leakage at the accident site.

Probable cause

the pilot's failure to assure an adequate fuel supply in order to complete the flight. A factor associated with the accident was the soft terrain on which the forced landing was made.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI98LA175
Event ID
20001211X10027
Case number
CHI98LA175
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: a212351baa76b4f289108e8a341919f27228924c4bbdccaf1065f09e7d0a2751; retrieved 2026-09-22T17:44:10.633Z.