ERA11CA262 · Cessna U206G
Associated Pilots Cessna U206G · Accident: runway excursion during landing
From Laurence G Hanscom Field (BED) to Laurence G Hanscom Field (BED)
Event
- NTSB case
- ERA11CA262
- 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
Cessna U206G
- Aircraft type
- Cessna 206
- 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
- N304EB
- Operator
- Associated Pilots
- Onboard fatalities
- Unknown
- Route
- From Laurence G Hanscom Field (BED), Bedford, MATo Laurence G Hanscom Field (BED), Bedford, MA
- 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
- Runway excursion
- 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 › 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 reported that he was approaching runway 3 in a slip with the flaps fully extended. During the flare, the airplane dropped suddenly, bounced, and became airborne again. The pilot stated that a quartering wind gust pushed the airplane to the left of the runway. He raised the flaps and added power in an attempt to go-around; but did not have enough area to clear trees located past the end of the runway. The pilot decreased the power, the airplane settled onto the runway, and then overran the runway into a swamp. The nose wheel plowed into the dirt and the airplane came to rest inverted, substantially damaging the wings and vertical stabilizer. The pilot stated he did not experience any mechanical problems with the airplane prior to the accident. Wind at the accident airport, recorded one hour prior to the accident was from 270 degrees at 10 knots, with gusts to 18 knots.
Probable cause
The pilot's inadequate compensation for the crosswind condition and his failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA262
- Event ID
- 20110424X11638
- Case number
- ERA11CA262
- 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: 0d74cb3235df02457e13561a7c716df9a19a4b2554bf618b50ad056b8229ad02; retrieved 2026-09-15T16:05:32.367Z.