CHI91DER12 · Lacey B D4
Lacey B D4 · Accident: on ground/water collision with terrain/water during takeoff
From an unrecorded airport to Rochester International Airport (RST)
Event
- NTSB case
- CHI91DER12
- 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
Lacey B D4
- Aircraft type
- Lacey B D4
- 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
- N363H
- Operator
- Daren C. Whipple · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Rochester International Airport (RST), Rochester, 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
- Takeoff
- 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
- On ground/water collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Remedial action, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PASSENGER REPORTED, 'ABOUT HALFWAY SOWN THE RUNWAY (DURING THE TAKEOFF ROLL) THE PILOT PUSHED THE STICK FORWARD AND LIFTED THE TAIL...IT APPEARED TO ME THAT THE PLANE TRIED TO LIFT OFF AT LEAST ONCE OR TWICE.' AS THEY NEARED THE END OF THE RUNWAY THE PASSENGER HEARD THE PILOT COMMENT ,'WE AREN'T GOING TO MAKE IT.' HE STATED THE AIRPLANE VEERED RIGHT AND CAME TO A SUDDEN STOP, NOSED DOWN IN A FIELD. A GROUND FIRE ENSUED, WHICH DESTROYED THE AIRCRAFT AND PILOT LOGBOOK RECORDS. THE AIRCRAFT WRECKAGE WAS REMOVED FROM THE FIELD WITH A FRONT END LOADER, AND WAS LOCATED IN A WOODED AREA WHEN EXAMINED BY FEDERAL INVESTIGATORS. THERE WAS NO EVIDENCE OF PRE IMPACT MALFUNCTION/DIFFICULTY. THE SHERIFF REPORTED THAT THE GRASS ON THE 2,500 FOOT LANG AIRSTRIP WAS TALL (ABOUT 6 INCHES) AND THE TEMPERATURE WAS 85 DEGREES FAHRENHEIT AT THE TIME OF THE ACCIDENT.
Probable cause
THE PILOT'S FAILURE TO TAKE ADEQUATE REMEDIAL ACTION. RELATED FACTORS ARE THE TALL GRASS RUNWAY CONDITIONS, AND THE INADEQUATE AIRSPEED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI91DER12
- Event ID
- 20001212X17474
- Case number
- CHI91DER12
- 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: fc936ac681dc5457e344d011e996a54541984d5245f52dfd542d0b3c099fe5d8; retrieved 2026-09-21T15:24:27.141Z.