ERA24LA401 · Remos Aircraft Gmbh GEMINI REMOS G-3/600
Remos Aircraft Gmbh GEMINI REMOS G-3/600 · Accident: dragged wing/rotor/float/other during landing
From an unrecorded airport to Frankfort-Highland Airport (6B4)
Event
- NTSB case
- ERA24LA401
- 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
- Event fatalities
- Unknown
- 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 GEMINI REMOS G-3/600
- Aircraft type
- Remos GEMINI REMOS G-3 600
- 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
- N5625T
- Operator
- Fred Northup
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Frankfort-Highland Airport (6B4), Utica/Frankfort, NY
- Aircraft age
- About 17 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
- Dragged wing/rotor/float/other
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he performed a preflight inspection of the float-equipped airplane. After engine start, warm up, and taxi, he began his takeoff roll from the lake. The pilot said the airplane took longer than normal to take off and once he was airborne his airspeed was only about 40-45 miles per hour. When he lowered the nose of the airplane to gain airspeed, the “right wing started to wave up and down,” consistent with a stall. The pilot attempted to land straight ahead on the lake, but upon touchdown, the right wing impacted the water, spinning the airplane, and collapsing the right float. During the impact sequence the outboard portion of the left wing was impact-separated, resulting in substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Therefore, it is most likely that the pilot did not obtain the proper airspeed or angle of attack on takeoff, which resulted in an aerodynamic stall and subsequent loss of control.
Probable cause
The pilot’s failure to maintain aircraft control on takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA401
- Event ID
- 20241209199395
- Case number
- ERA24LA401
- 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, cause areas. 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: 873a26fd2d32156b36bb040e7d689e70de9f38a00252095082b355f7373e70b6; retrieved 2026-09-16T19:31:39.724Z.