CHI90LA210 · Piper J-3 CUB
Piper J-3 CUB · Accident: in flight encounter with weather en route
From Harbor Springs, MI (no airport) to Oshkosh, WI (no airport)
Event
- NTSB case
- CHI90LA210
- 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
- Instrument Meteorological Cond
Piper J-3 CUB
- Aircraft type
- Piper J-3
- 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
- N1455N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Harbor Springs, MI (no airport)To Oshkosh, WI (no airport)
- 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
- In flight encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s); Wire, static
- 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 › Clearance, not maintained
- Pilot in command › Visual lookout, inadequate
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE PILOT STATED THAT HE WAS FLYING ACROSS THE LAKE AT ABOUT 500' AGL. HE REPORTED THAT WHEN THE AIRCRAFT CROSSED OVER THE SHORELINE ONTO LAND 'THE VISIBILITY SUDDENLY BECAME OBSCURED.' THE PILOT PERFORMED A 180 DEGREE TURN AND BEGAN TO DESCEND, INTENDING TO LAND HIS FLOAT PLANE ON THE LAKE ALONG THE SHORELINE. THE AIRCRAFT COLLIDED WITH TREES AND POWER LINES DURING THE DESCENT, AND FELL TO THE GROUND.
Probable cause
PILOT'S FAILURE TO MAINTAIN AN ADEQUATE VISUAL LOOKOUT DURING THE DESCENT. CONTRIBUTING FACTORS ARE THE PILOT'S POOR WEATHER EVALUATION, AND CONTINUED VFR FLIGHT INTO IFR CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA210
- Event ID
- 20001212X23665
- Case number
- CHI90LA210
- 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: 0189ab10368c590d4669e48be27cdcf19ac9e2ccbb8185ada767f85f075db4f6; retrieved 2026-09-23T05:29:29.095Z.