IAD98LA064 · Cessna 172D
Cessna 172D · Accident: loss of control in flight during landing
From Portsmouth International Airport at Pease (PSM) to Beverly Regional Airport (BVY)
Event
- NTSB case
- IAD98LA064
- 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
- 0
- 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 172D
- Aircraft type
- Cessna 172
- 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
- N2507Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portsmouth International Airport at Pease (PSM), Portsmouth, NHTo Beverly Regional Airport (BVY)
- 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 in flight
- 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 › Aircraft control, not maintained
Approximate · Estimated position: the centre of Beverly, MA, the place the record names. Not the accident site.
NTSB narrative
The pilot reported that as she flared the airplane for landing on runway 34, a gust of wind turned the airplane 30 degrees to the left. She stated that she immediately added full power to go around, but the airplane continued to drift left. At midfield, according to the pilot, nothing looked right; and still unable to control the airplane, she pulled the power off and attempted to land in a field adjacent to the runway. The pilot indicated that events happened so quickly, she did not remember the left wing contacting the ground. The wind was reported to be from 320 degrees at 12 knots. The pilot reported that she did not have any mechanical problems with the airplane. An FAA Inspector reported that the airplane traveled 550 feet from the runway before coming to a stop in an upright position. The Inspector reported that the left wing contacted the ground, leaving the outboard 16 inches of the wing bent up, and the aileron bent down. Further examination of the wing revealed damage to the trailing edge spar.
Probable cause
failure of the pilot to maintain control of the airplane during the landing and attempted go-around. A related factor was the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98LA064
- Event ID
- 20001211X10113
- Case number
- IAD98LA064
- 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. 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: 5ca1a29bf1795993d6408b0acc596da83d1879b998f5527b84eadde7a4868f7d; retrieved 2026-09-22T17:43:47.810Z.