ERA12FA395 · Remos Acft Gmbh Flugzeugbau REMOS GX
Remos Acft Gmbh Flugzeugbau REMOS GX · Accident: flight control system malfunction/failure en route
From Frederick Municipal Airport (FDK) to Piseco Airport (K09)
Event
- NTSB case
- ERA12FA395
- 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
- 1 · 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 Acft Gmbh Flugzeugbau REMOS GX
- Aircraft type
- Remos GX
- 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
- N206GX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Frederick Municipal Airport (FDK), Frederick, MDTo Piseco Airport (K09), Piseco, NY
- 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
- En route · cruise
- 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
- Flight control system malfunction/failure
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The special-light sport airplane was designed with the ability to fold both wings back to facilitate storage and transportation. In addition, both wings and the horizontal stabilizer were removable. The pilot, who was also a mechanic, disassembled the airplane for storage during the winter. He subsequently reassembled it and completed a condition inspection. He then flew the airplane to an airport where a ballistic parachute system was installed. The pilot then flew the airplane to another airport and, the next day, departed on the accident flight with the intention of delivering the airplane to its owner.
About 20 minutes after takeoff, the airplane experienced a disconnected elevator, and the pilot attempted to fly to a nearby airport. The airplane was about 50 feet above the ground when it entered a sudden steep pitch downward and impacted the ground about 60 feet before the runway.
The airplane's flight controls were actuated by a series of push-pull rods. The respective push-pull rods for the left and right ailerons and elevator controls featured a "quick-fastener" to disconnect and reconnect the respective flight control. Postaccident examination of the airplane revealed that the elevator quick-fastener was disconnected. Additional examination of the quick-fastener revealed that it contained some corrosion; however, it did not experience any failures and was capable of functioning as designed. In addition, the ballistic parachute system parachute was not activated, and the activation handle, which was mounted on the center console, was found secured with a padlock. The key for the padlock was found on a key ring with the ignition key, which remained inserted in the ignition switch.
The preflight checklist located in the pilot operating handbook required a check of the quick-fasteners and the ballistic parachute activation handle before every flight. Associated placards were also present in the cockpit. The pilot had at least three opportunities to identify an improperly secured elevator quick-fastener since he assembled the airplane; at least two of those opportunities occurred after the installation of the ballistic recovery parachute system. While it could not be determined if the pilot would have used the airplane's ballistic recovery parachute system, his failure to remove the padlock from the activation handle precluded the option of deploying the system during the accident flight.
Probable cause
The pilot's inadequate preflight inspection, which failed to ensure that the elevator quick-fastener was properly secured, resulting in an inflight elevator control disconnect and subsequent loss of control during the ensuing emergency landing. Contributing to the accident was the pilot's failure to remove the padlock from the airplane's ballistic recovery system parachute activation handle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA395
- Event ID
- 20120615X34118
- Case number
- ERA12FA395
- 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: e2cd37640779a28905bd370c49467ea7f9f0a7af0be168f35975acacc7c6bbce; retrieved 2026-09-13T22:26:54.247Z.