CEN11CA354 · Henry Slosing Lanceair
Henry Slosing Lanceair · Accident: loss of control on ground during landing
From Wichita, KS to Double Eagle II Airport (AEG)
Narrative check · The NTSB narrative appears to contradict this record's location and departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11CA354
- 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
Henry Slosing Lanceair
- Aircraft type
- Henry Slosing LANCEAIR
- 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
- N79BC
- Operator
- Abraham Brant C
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Wichita, KSTo Double Eagle II Airport (AEG), Albuqurque, NM
- 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
- Defining eventThe 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 on ground
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot had just touched down with a 12-knot crosswind when the wind suddenly gusted to 36 knots and pushed the airplane off the runway. The pilot stated that he attempted to fly out of the condition by adding power, and the airplane became airborne about three times; however, the landing gear became side-loaded and the right gear collapsed. The left wing also contacted the ground and sustained a two foot-wide gouge in the leading edge. The sudden wind shift/gust was confirmed by the tower air traffic controller and approximately one hour later the airport's automated weather observation system reported the wind shifted to 240 degrees and increased to 21 knots gusting to 28 knots.
Probable cause
The pilot’s loss of directional control while landing in gusty conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA354
- Event ID
- 20110525X20351
- Case number
- CEN11CA354
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 475f6564b8f37a5191308463dd22031e93ecbcfe3715a1735b52d1d64888e766; retrieved 2026-09-15T16:12:22.206Z.