FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25LA068 · Remos Aircraft Gmbh REMOS G-3/600

21 Dec 2024 · Brawley, CA, United States

Remos Aircraft Gmbh REMOS G-3/600 · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
WPR25LA068
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

Remos Aircraft Gmbh REMOS G-3/600

Aircraft type
Remos G-3
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
N191DY
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
Approach · VFR pattern final
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 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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot stated that the purpose of the flight was to gain familiarity with the airplane under the supervision of a flight instructor. Following departure, they performed serval touch-and-go takeoffs and landings at a nearby airport before returning back to the departure airport. After configuring the airplane for landing and maintaining a stabilized approach, the student pilot prepared for the landing flare. As the airplane crossed over the runway threshold, the airplane suddenly descended and impacted the runway surface hard. The airplane became airborne and veered to the left of the runway centerline. The airplane continued off the runway and impacted a taxiway marker and the windsock pole resulting in it spinning 180° before coming to rest. As a result of the impact the airplane incurred substantial damage to the left wing. The student pilot reported no preimpact mechanical anomalies or malfunctions that could have precluded normal operation.

Probable cause

The flight instructor’s lack of remedial action to the student pilot’s inadequate landing flare, which resulted in a hard landing and a loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR25LA068
Event ID
20241223199462
Case number
WPR25LA068
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-12-22.
  • API snapshot SHA-256: 2f56582f2458bc930cc66260a03d71ba6be4b84c27e2a0a9d2a9d187aae19c84; retrieved 2026-09-16T19:33:48.545Z.