MIA08CA194 · Glasflugel H-301
Glasflugel H-301 · Accident: abnormal runway contact during landing
From Blairstown Airport (1N7) to Blairstown Airport (1N7)
Event
- NTSB case
- MIA08CA194
- 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
Glasflugel H-301
- Aircraft type
- Glasflugel H-301
- Category
- Glider
- 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
- N1263
- Operator
- Rudolf K. Braun · private individual
- Onboard fatalities
- Unknown
- Route
- From Blairstown Airport (1N7), Blairstown, NJTo Blairstown Airport (1N7), Blairstown, NJ
- 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 · 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated he was conducting a personal flight and flew around the local area before returning to his departure airport. He entered a left downwind for runway 25 and completed his before-landing checks. The winds were reported to be out of the west at 16 knots gusting to 26 knots. He lowered flaps, extended the speed brakes, and turned on final approach. The landing flare was initiated over the runway and he reached over to retract the speed brakes, and inadvertently retracted the flaps. The glider collided with the runway hard and came to a stop. The pilot exited the glider without assistance and without injury. Examination of the glider revealed that the tail section of the glider received structural damage. The pilot stated he did not experience any mechanical problems with the glider before the accident.
Probable cause
The pilot's inadvertent retraction of flaps during the landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08CA194
- Event ID
- 20081003X42131
- Case number
- MIA08CA194
- 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: 4b1aa4b8b3dd23e95ae52033bb1c95599ee4a13c2b08f384dd32ba6bc75354c7; retrieved 2026-09-15T10:20:41.699Z.