CHI83LA098 · Gulfstream AMERICAN AA-5B AMERICAN A
Gulfstream AMERICAN AA-5B AMERICAN A · Accident: dragged wing, rotor, pod, float or tail/skid during landing
Event
- NTSB case
- CHI83LA098
- 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
Gulfstream AMERICAN AA-5B AMERICAN A
- Aircraft type
- Gulfstream AMERICAN AA-5B
- 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
- N209JA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Dragged wing, rotor, pod, float or tail/skid
- 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/mush
- 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 › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT DURING ARRIVAL, HE CONTACTED UNICOM FOR AN ADVISORY. REPORTEDLY, THE WIND AT THAT TIME WAS FROM 090 DEG AT 15 KTS, WITHIN THE X-WIND CAPABILITY OF THE ACFT. DURING THE APPROACH AND LANDING, THE PLT SLIPPED THE PLANE TO A NORMAL RIGHT-WHEEL TOUCHDOWN ON RWY 36. AT ABOUT THAT TIME, A HEAVY GUST WAS ENCOUNTERED AND THE ACFT LIFTED OFF AGAIN. THE PLT APPLIED POWER AND RETURNED OVER THE RWY FOR A 2ND ATTEMPT TO LAND. ANOTHER GUST WAS ENCOUNTERED AND THE LEFT WING TIP STRUCK THE GROUND. THE PLT ADDED POWER TO GO AROUND. REPORTEDLY, THE AIRSPEED WAS SLOW AND THE ACFT DRIFTED TO THE WEST TOWARD A WATER TOWER AND OTHER OBSTACLES. SUBSEQUENTLY, THE ACFT MUSHED INTO A ROUGH FIELD AND COLLIDED WITH A FENCE. THE PILOT ESTIMATED THAT THE WIND HAD GUSTED TO 30 KTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI83LA098
- Event ID
- 20001214X42151
- Case number
- CHI83LA098
- 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: c805250010ba84cab604dd7fdbcf19d0855bbe5514ceef161f4a2c31e5fe6504; retrieved 2026-09-23T23:18:07.504Z.