CHI88DEP06 · Huntley CHALLENGER II CHALLENGER
Huntley CHALLENGER II CHALLENGER · Accident: partial loss of engine power (non-mechanical) during initial climb
From an unrecorded airport to 47C · Boscobel, WI
Event
- NTSB case
- CHI88DEP06
- 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
Huntley CHALLENGER II CHALLENGER
- Aircraft type
- Huntley CHALLENGER
- 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
- N51012
- Operator
- Huntley, John D. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 47C · Boscobel, 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
- Initial climb
- 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
- Partial 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
- Pilot in command › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER CLIMBING ABOUT 100' AFTER TAKEOFF, A PARTIAL POWER LOSS OCCURRED & THE PLT INITIATED A LEFT TURN TO RTRN TO THE ARPT. UNABLE TO REACH THE ARPT, AN EMERG LNDG WAS MADE IN A CORN FIELD & THE ACFT WAS DAMAGED. NO AIRFRAME FAILURE WAS FOUND & THE ENG RAN NORMALLY DRG AN OPERATIONAL CHECK. THE PLT NOTED THAT SVRL BAGS & A PURSE WERE STOWED AFT OF THE REAR PASSENGER SEAT ON TOP OF THE PLASTIC FUEL TANK (JUG). THERE WAS A FLEXIBLE FUEL LINE THAT WAS ROUTED FROM THE TOP OF THE FUEL JUG TO THE ENG. AN INVESTIGATION SHOWED THAT IF THE FLEXIBLE FUEL LINE HAD BECOME KINKED OR IF THE VENT ON TOP OF THE JUG HAD BEEN BLOCKED, FUEL FLOW TO THE ENG WOULD HAVE BEEN RESTRICTED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI88DEP06
- Event ID
- 20001213X26147
- Case number
- CHI88DEP06
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-07-12.
- API snapshot SHA-256: 3a4a7ef664a479169593244d732e6cb9b5d7b8cce1e26e3a5a34e695037560bf; retrieved 2026-09-23T09:39:50.797Z.