WPR24LA272 · Renquist George GS-2 SPORTSMAN
Renquist George GS-2 SPORTSMAN · Accident: hard landing
Event
- NTSB case
- WPR24LA272
- 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
Renquist George GS-2 SPORTSMAN
- Aircraft type
- Renquist George GS-2
- 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
- N552GC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 16 years (built 2008)
- 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
- Hard landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and owner of the tailwheel equipped airplane reported that he was performing a short field approach with a flight instructor. During the landing, the instructor took control of the aircraft and pulled the control stick back, to increase the airplane’s pitch, and did not increase engine power. The airspeed decayed and the airplane experienced an aerodynamic stall and landed hard. The flight instructor reported that the sport pilot/owner was at the controls during the short field approach, and he had been talking him through the approach. On final approach, the instructor told the pilot to lower the nose and add power. Subsequently, the flight instructor applied full engine power, however, the airplane landed hard, which resulted in substantial damage to the fuselage. The instructor and the pilot both reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The flight crew’s failure to maintain airspeed during a short field landing and the instructor’s delayed remediation, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24LA272
- Event ID
- 20240812194909
- Case number
- WPR24LA272
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-08-08.
- API snapshot SHA-256: 849700621bd18cd46f948fb7fe56f97b6e0d3b2451e4e97f4761bffda491fe6b; retrieved 2026-09-16T19:09:37.641Z.