FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA143 · Rose 75% Scale Fokker D8

25 May 2002 · Derby, KS, United States

Rose 75% Scale Fokker D8 · Accident: loss of control in flight during initial climb

From 1K3 · Derby, KS to an unrecorded destination

Report a problem

Event

NTSB case
CHI02LA143
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

Rose 75% Scale Fokker D8

Aircraft type
Rose 75
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
N2188X
Operator
Unknown
Onboard fatalities
Unknown
Route
From 1K3 · Derby, KSTo 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
Loss of control in flight
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
Tree(s)
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 › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained
  • Pilot in command › Preflight planning/preparation, inadequate

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 contacted trees following a loss of directional control during takeoff. The pilot reported he was short on runway when he initiated the takeoff so he had to "prematurely pull the aircraft off the ground... ." The pilot stated that once airborne the wind pushed the airplane toward a line of trees. He reported that he attempted to straighten the airplane heading, but instead the airplane hit the trees at an altitude of about 10 feet above the ground. The airplane contacted trees along the right side of the runway. The pilot reported the winds were out of the west at 15 knots. The pilot reported that the ailerons are ineffective until reaching 60 mph. He also reported that the rudder was so sensitive that at 50 mph, 1- inch of rudder pedal displacement would result in a 180 degree flat turn.

Probable cause

Inadequate preflight planning and inadequate compensation for the wind conditions which resulted in a failure to maintain directional control of the airplane. Factors associated with the accident were the crosswind and the trees which the airplane contacted during the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA143
Event ID
20020528X00740
Case number
CHI02LA143
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: 77f47f1ac03dfd89b8d62406f621f88e41c3b5ff748e9296057242e5f1bba418; retrieved 2026-09-21T19:43:35.258Z.