FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI85LA307 · Bellanca 17-30

21 Jul 1985 · Sheboygan, WI, United States

Bellanca 17-30 · Accident: total loss of engine power (non-mechanical) en route

From WASHINGTON IS, WI to Sheboygan County Memorial Airport (SBM)

Report a problem

Event

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

Bellanca 17-30

Aircraft type
Bellanca 17
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
N7315V
Operator
Unknown
Onboard fatalities
Unknown
Route
From WASHINGTON IS, WITo Sheboygan County Memorial Airport (SBM), Sheboygan, WI
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 · 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 (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 starvation
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 › Starvation

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

NTSB narrative

THE ACFT COLLIDED WITH A DITCH DURING A FORCED LANDING FOLLOWING A LOSS OF POWER IN CRUISE FLT. THE PLT REPORTED HE SWITCHED THE FUEL SELECTOR FROM THE LEFT TO THE RIGHT TANK, & AFTER APRX 3 MINUTES, A TOTAL LOSS OF POWER WAS EXPERIENCED. HE STATED THAT REPEATED ATTEMPTS TO RESTART THE ENGINE WERE FUTILE. HE NOTED THAT AFTER THE POWER LOSS, THE FUEL PRESSURE DROPPED OFF. WHEN HE TURNED ON THE AUX FUEL PUMP, THERE WAS NO FUEL PRESSURE INDICATION. A POST ACCIDENT INSPECTION OF THE ACFT DISCLOSED NO MECHANICAL FAILURE/MALFUNCTION. THE RIGHT MAIN FUEL TANK CONTAINED 6 1/2 INCHES OF FUEL & THE LEFT MAIN TANK CONTAINED 1 1/4 INCHES OF FUEL (MAIN TANKS PLACARDED 19 GAL CAPACITY). BOTH THE LEFT & RIGHT AUX TANKS WERE EMPTY.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI85LA307
Event ID
20001214X37059
Case number
CHI85LA307
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: 239825fefd29d56eb72f9eefd085ec1a7197a39b2827577c8c8daf3bc22a1a41; retrieved 2026-09-23T16:41:03.007Z.