CHI08CA007 · Krueger Quickie
Krueger Quickie · Accident: forced landing while maneuvering
From Antigo, WI to an unrecorded destination
Event
- NTSB case
- CHI08CA007
- 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
Krueger Quickie
- Aircraft type
- Krueger QUICKIE
- 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
- N5425D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Antigo, 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
- Maneuvering · turn to reverse direction
- 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
- Forced landing
- 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 › Airspeed, not obtained/maintained
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Proper climb rate, not obtained/maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane received substantial damage during a forced landing. The pilot reported that, while practicing a high speed taxi, the nose lifted off when the airplane was about halfway down the runway. The pilot elected to continue the climb in order get a "feel of the plane" and return to the runway rather than attempting to "force" a landing on the remaining runway in an "awkward" situation. During the return to the runway, the airplane reportedly could not maintain altitude because it was behind the "power curve." The pilot then attempted an off airport landing on a field during which the airplane impacted a group of trees along the field edge. The pilot had accumulated a total flight time of 0.3 hours in the make and model of accident airplane.
Probable cause
The inadequate preflight planning and preparation by the pilot, the proper climb rate not obtained/maintained by the pilot, and the airspeed not obtained/maintained by the pilot. Contributing factors were the lack of total experience in the type of aircraft and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA007
- Event ID
- 20080103X00011
- Case number
- CHI08CA007
- 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: fca73d0ed8dbcafa7358e74646be9126dab45ce5e7c379b2e75d2979c8c42553; retrieved 2026-09-21T08:43:12.029Z.