CEN10CA239 · Remos Aircraft Gmbh G-3/600
U S Aviation Group Remos Aircraft Gmbh G-3/600 · Accident: loss of control in flight during takeoff
From Perot Field/Fort Worth Alliance Airport (AFW) to Perot Field/Fort Worth Alliance Airport (AFW)
Event
- NTSB case
- CEN10CA239
- 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
Remos Aircraft Gmbh 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
- N265RA
- Operator
- U S Aviation Group
- Onboard fatalities
- Unknown
- Route
- From Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TXTo Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TX
- 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
- Takeoff
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff the student pilot experienced trouble controlling the light sport airplane. The flight instructor took over the controls and, believing that the airplane’s flight controls might have been malfunctioning, elected to land on the remaining runway. The fiberglass airplane impacted the runway hard, which resulted in a propeller strike and the collapse of the nose landing gear and left main landing gear. The airplane came to rest on the runway in an upright and left-wing-low position. Following an engine shutdown, the instructor and student were able to exit unassisted. Around the time of the accident the wind was shifting back and forth from a quartering headwind to a quartering tailwind. A Federal Aviation Administration inspector examined the airplane and reported that no preimpact anomalies were noted with the airplane’s flight controls.
Probable cause
The student pilot’s loss of control and the instructor’s delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA239
- Event ID
- 20100505X60615
- Case number
- CEN10CA239
- 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. 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: b8317cba860472ca762452d4894d68928b06a67d51c327739c064b22bd871753; retrieved 2026-09-15T13:59:58.065Z.