CHI92LA085 · Piper PA-32R-300
Pribyls Wings Piper PA-32R-300 · Accident: airframe, component or system failure en route
From Ingersoll Airport (CTK) to Y33 · Maple Lake, MN
Event
- NTSB case
- CHI92LA085
- 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
Piper PA-32R-300
- Aircraft type
- Piper PA-32
- 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
- N427KP
- Operator
- Pribyls Wings
- Onboard fatalities
- Unknown
- Route
- From Ingersoll Airport (CTK), Canton, ILTo Y33 · Maple Lake, MN
- 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
- Airframe, component or system failure
- 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
- Pilot in command › Emergency procedure, not performed
- Pilot in command › Emergency procedure, not understood
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING AN IFR FLIGHT THE PILOT NOTICED A GRADUAL LOSS OF ELECTRICAL POWER DUE TO A FAULTY VOLTAGE REGULATOR. THE PILOT REQUESTED A CHANGE IN ROUTING FROM ARTCC WITH THE INTENTION OF LANDING. ACCORDING TO THE PILOT, HE CIRCLED OVER THE AIRPORT UNTIL RECEIVING A GREEN LIGHT FROM THE ATC TOWER. WHILE ON FINAL APPROACH FOR LANDING THE PILOT RECEIVED A RED LIGHT FROM THE TOWER. THE PILOT INITIATED A GO-AROUND MANEUVER AND BEGAN HIS SECOND APPROACH SHORTLY THEREAFTER. THE AIRPLANE MADE A GEAR-UP LANDING DURING THE SECOND LANDING APPROACH. WHEN ASKED IF HE UTILIZED THE EMERGENCY GEAR EXTENSION SYSTEM THE PILOT STATED HE DID NOT BECAUSE HE THOUGHT HE FELT THE LANDING GEAR DRAG.
Probable cause
A RESULT OF THE PILOT-IN-COMMAND NOT UNDERSTANDING THE AIRPLANES EMERGENCY PROCEDURES AND NOT PERFORMING THE APPROPRIATE EMERGENCY PROCEDURES. A FACTOR ASSOCIATED WITH THE ACCIDENT WAS AN ELECTRICAL SYSTEM FAILURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA085
- Event ID
- 20001211X14080
- Case number
- CHI92LA085
- 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: b8f7f666cf67b48d4c6b43fcee2390364aae8389b5345dff37c997da729271ad; retrieved 2026-09-23T03:24:10.705Z.