IAD02LA017 · Cessna 152
Cessna 152 · Accident: loss of control on ground/water during landing
From N99 · West Chester, PA to N99 · West Chester, PA
Event
- NTSB case
- IAD02LA017
- 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
- N58ND
- Operator
- Adel Barimani
- Onboard fatalities
- Unknown
- Route
- From N99 · West Chester, PATo N99 · West Chester, PA
- 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
- First occurrenceThe 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
- Loss of control on ground/water
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the downwind leg of the traffic pattern, the pilot felt that the airplane was "being pulled" to the left. As the airplane touched down on runway 27, it veered off the left side, crossed a grass area, and stopped short of an aircraft hangar. The pilot reported that he checked the windsock prior to takeoff and again before landing, and it indicated wind out of the southwest at about 5-7 knots. He stated that he normally corrected for a crosswind by "flying the airplane into the wind." He also stated that the airplane veered off the runway as he was repositioning his feet from the rudder pedals to the brake pedals. The pilot did not report any mechanical deficiencies with the airplane. He also reported 115 hours of total flight time, 94 of which were in make and model.
Probable cause
The pilot's failure to maintain directional control of the airplane during landing. A factor was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02LA017
- Event ID
- 20011210X02376
- Case number
- IAD02LA017
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: faac99650b162817e8dd4c006729333c57273ee2da81245c4cc7789618bde05c; retrieved 2026-09-22T11:20:43.326Z.