ERA11CA329 · Remos Aircraft Gmbh REMOS G-3/600
First Landings Aviation Remos Aircraft Gmbh REMOS G-3/600 · Accident: loss of control in flight during landing
From Orlando Apopka Airport (X04) to Orlando Apopka Airport (X04)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA11CA329
- 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 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
- N13GX
- Operator
- First Landings Aviation
- Onboard fatalities
- Unknown
- Route
- From Orlando Apopka Airport (X04), Apopka, FLTo Orlando Apopka Airport (X04), Apopka, FL
- 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
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident flight was the student pilot's first solo flight. The certified flight instructor conducted several landings with the student prior to the solo portion of the flight. During the solo, the student pilot took off without incident and entered the traffic pattern. While on final approach to land, as the student got close to the ground, the aircraft encountered a wind gust that pushed the aircraft to the left. The student pilot stated that he used right aileron to correct for the wind but was unable to stop the drift. The airplane touched down to the left of the runway and then became airborne again. The student pilot then attempted to land on an adjacent taxiway, where the propeller struck a taxiway sign and the left wing impacted a hangar. A postaccident examination revealed that the airplane had incurred substantial damage to the left wing and firewall. There was no evidence of any preimpact failure or malfunction of the airplane or engine.
Probable cause
The pilot's failure to maintain directional control during landing, which resulted in a runway excursion and collision with a hangar.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA329
- Event ID
- 20110609X91648
- Case number
- ERA11CA329
- 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: 1f2602c49b24ca2f0af8992393e9a588aa9e582a3dcd47d92c50c3bc25371acb; retrieved 2026-09-15T16:16:01.170Z.