CHI93LA237 · Daniel Squire HI-MAX
Daniel Squire HI-MAX · Accident: in flight collision with object during initial climb
From Winneconne, WI to an unrecorded destination
Event
- NTSB case
- CHI93LA237
- 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
Daniel Squire HI-MAX
- Aircraft type
- Daniel Squire HI-MAX
- 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
- N200D
- Operator
- Daniel G. Squier · private individual
- Onboard fatalities
- Unknown
- Route
- From Winneconne, WITo not recorded
- 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
- In flight collision with object
- 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
- Wire, transmission
- 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 › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE TOOK OFF IN A WESTERLY DIRECTION FROM A PRIVATE, GRASS STRIP THAT WAS BORDERED BY WIRES AND TREES AT THE WEST END. HE SAID THAT THE AIRPLANE REACHED AN ALTITUDE OF APPROXIMATELY 50' ABOVE THE GROUND AND WOULDN'T CLIMB ANY HIGHER. HE FEELS THE AIRPLANE WOULDN'T CLIMB ANY HIGHER DUE TO A DOWNDRAFT CREATED BY A WESTERLY FLOW OF WIND OVER THE TREES LOCATED AT THE WEST END OF THE RUNWAY. THE AIRPLANE COLLIDED WITH THE WIRES AT THE WEST END OF THE FIELD AND CRASHED. NO PREIMPACT MECHANICAL PROBLEMS WITH THE AIRPLANE WERE REPORTED BY THE PILOT.
Probable cause
the pilot's inadequate preflight planning and preparation. A factor in the accident is the downdraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93LA237
- Event ID
- 20001211X12592
- Case number
- CHI93LA237
- 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: 2828e2986b2dd231a0ef45e23732d6a96add7ec7961e74efcb208ae17f897ff2; retrieved 2026-09-21T14:20:33.784Z.