CHI97LA010 · Dellicker STARDUSTER TOO SA300 STARDUSTER
Dellicker STARDUSTER TOO SA300 STARDUSTER · Accident: abrupt maneuver during initial climb
From Skyway Estates Airport (60G) to an unrecorded destination
Event
- NTSB case
- CHI97LA010
- 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
- 2 · 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
Dellicker STARDUSTER TOO SA300 STARDUSTER
- Aircraft type
- Dellicker STARDUSTER TOO SA300
- 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
- N7691
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Skyway Estates Airport (60G)To 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
- Abrupt maneuver
- 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
- Stall
- 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 › Airspeed, inadequate
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A private pilot, who was a witness to the accident, reported that he observed the airplane depart. 'After breaking ground contact, the airplane leveled off, gained airspeed, and then near the end of the runway, the pilot pulled up sharply into a steep climb. After a couple of hundred of feet of climb [the airplane] entered a steep right turn of approximately 45 degrees. The aircraft lost control and fell to the ground and crashed.' The witness reported that he did not hear any 'unusual' sound, and he believed the engine was at full power. A second witness reported that he noticed an airplane 'going 90 degrees straight up and straight down.' One propeller blade was bent near the root in the aft direction and exhibited minor torsional bending. The other blade exhibited minor 's' shaped bending.
Probable cause
the pilot's failure to maintain adequate airspeed and subsequent inadvertent stall of the airplane. A factor was the ostentatious display.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA010
- Event ID
- 20001208X06856
- Case number
- CHI97LA010
- 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: e1cccbbfbe398bbfce46292d975fa5e9eea60485573239ab758a26486eac3002; retrieved 2026-09-20T23:10:08.048Z.