CHI99LA113 · Delong GLASTAR GS-1 GLASTAR GS
Delong GLASTAR GS-1 GLASTAR GS · Accident: loss of control in flight during landing
From D95 to an unrecorded destination
Event
- NTSB case
- CHI99LA113
- 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
Delong GLASTAR GS-1 GLASTAR GS
- Aircraft type
- Delong GLASTAR GS-1
- 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
- N918V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From D95To 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
- Landing · flare/touchdown
- 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
- 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, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot's written statement, the pilot 'experienced [wind] shear on short final to runway 27...' A weather report for a reporting station located 21 nautical miles and 253 degrees from the accident site reported winds from 200 degrees at 11 knots. According to the 1999 Michigan Airport Directory, the runway that was used has several groupings of trees along both sides of the runway. Post accident investigation revealed damage to the right wing, propeller, nose landing gear, and fuselage substructure. Further examination revealed no pre-existing anomalies.
Probable cause
The failure of the pilot to maintain compensation for wind conditions. Factors to the accident were the crosswind condition and the presence of trees along the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA113
- Event ID
- 20001205X00288
- Case number
- CHI99LA113
- 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: 73823666cc6efeac731ef1f881e6660c4d32b4ad9334d89e7266c3230741e49c; retrieved 2026-09-22T15:39:31.870Z.