GAA16CA148 · Remos Aircraft Gmbh G 3/600
Remos Aircraft Gmbh G 3/600 · Accident: abnormal runway contact during landing
From Lawrence County Airpark (HTW) to Lawrence County Airpark (HTW)
Event
- NTSB case
- GAA16CA148
- 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
- N201RQ
- Operator
- Donald Lee
- Onboard fatalities
- Unknown
- Route
- From Lawrence County Airpark (HTW), CHESAPEAKE/HUNTINGTON WVA, OHTo Lawrence County Airpark (HTW), CHESAPEAKE/HUNTINGTON WVA, OH
- Aircraft age
- About 9 years (built 2007)
- 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
- Abnormal runway contact
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, during final approach, his airspeed was too fast. He reported that he decided to extend the landing flare in ground effect in order to bleed off the excess airspeed. As the airplane's main landing gear touched down on the runway, the airplane bounced. The pilot reported that when the airplane settled back on the runway, the nose gear collapsed and the airplane exited the runway to the left. The airplane sustained substantial damage to the firewall and the composite fuselage floorboard.
The pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.
Probable cause
The pilot's unstable approach, which resulted in excessive airspeed during the touchdown, subsequent bounced landing, collapsed nose landing gear, and a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA148
- Event ID
- 20160315X02010
- Case number
- GAA16CA148
- 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: 376fad0f7fb600eb9418bd149137f2fb1a46af768ecbfc0e50a326dfa39c6245; retrieved 2026-09-16T03:13:11.790Z.