FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07LA224 · Beech V35B

21 Jul 2007 · Rockford, IL, United States

Beech V35B · Accident: loss of engine power en route

From Chicago Rockford International Airport (RFD) to Wittman Regional Airport (OSH)

Report a problem

Event

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

Beech V35B

Aircraft type
Beechcraft 35
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
N313W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago Rockford International Airport (RFD), Rockford, ILTo Wittman Regional Airport (OSH), Oshkosh, 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
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

  • Reason for occurrence undetermined

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 executed a forced landing following a loss of engine power during cruise flight. The airplane was part of a formation flight at the time of the initial loss of engine power. The pilot stated that about 10 minutes after takeoff, the engine "began to hesitate during large throttle excursions and faltered upon [application of] full throttle." He left the formation with the intention of returning to the departure airport. However, "the engine began making loud noises and the RPM sagged to 2,000," with the manifold pressure approximately 10 inches. He subsequently executed a forced landing to a cornfield. A post accident engine examination did not reveal any anomalies associated with a pre-impact engine failure. The engine assembly was subsequently run on a test stand for approximately 30 minutes. No anomalies were detected during the engine run.

Probable cause

A loss of engine power for undetermined reasons, which resulted in a forced landing. A contributing factor was the unsuitable terrain (corn field) encountered during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07LA224
Event ID
20070808X01140
Case number
CHI07LA224
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: 861c129d0e78a0d728995b8496b11bfa98d3e6dc97509fe42c9833a01b06e971; retrieved 2026-09-22T03:37:50.872Z.