ERA10CA369 · Cessna 152
Cessna 152 · Accident: runway excursion during landing
From Maryland Airport (2W5) to Maryland Airport (2W5)
Event
- NTSB case
- ERA10CA369
- 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 152
- Aircraft type
- Cessna 152
- 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
- N4823B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Maryland Airport (2W5), Indian Head, MDTo Maryland Airport (2W5), Indian Head, MD
- 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 · landing roll
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he received a weather briefing that stated there was a convective SIGMET (significant meteorological information) over the airport and the storm would be arriving in about one hour. After receiving the briefing, the pilot performed a preflight check on the airplane, and proceeded to take off on a local solo flight. The pilot stated that during different phases of each traffic pattern, he had difficulty due to the gusty wind conditions. After initiating a go-around on the original departure runway, the pilot elected to set up for a long approach to a different runway. While on final approach, the airplane encountered gusty conditions and the pilot attempted to compensate for a crosswind. During touchdown, the airplane bounced several times, overran the end of the runway, and collided with a small ditch resulting in damage to the firewall. The pilot reported that there were no mechanical failures or malfunctions with the airplane. The recorded wind conditions about the time of the accident at an airport 8 miles away indicated a velocity of 10 knots, gusting to 18 knots.
Probable cause
The pilot's loss of control while landing in gusting crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA369
- Event ID
- 20100721X52136
- Case number
- ERA10CA369
- 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: 4a1110210decf47e614b16b1c3e32f2a775ab687f09d9795b9d05ca49ba1a677; retrieved 2026-09-15T14:44:12.563Z.