IAD97FA001 · Piper PA-32-300
Piper PA-32-300 · Accident: in flight collision with terrain/water on approach
From N52 · Somerville, NJ to W32 · Clinton, MD
Event
- NTSB case
- IAD97FA001
- 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
- 3 · 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
- Instrument Meteorological Cond
Piper PA-32-300
- Aircraft type
- Piper PA-32
- 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
- N2881W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From N52 · Somerville, NJTo W32 · Clinton, 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
- Approach · circling (IFR)
- 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
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was receiving vectors from air traffic control for a visual approach to Hyde Field Airport. The pilot was in instrument meteorological conditions and attempting to acquire visual meteorological conditions to conduct the landing. The last assigned altitude given to the pilot by ATC was 1600 feet, which was the minimum vectoring altitude for that area. The pilot radioed ATC and informed them that he was descending to 1000 feet. ATC did not respond to the pilot's radio call. The airplane descended to 1000 feet, circled 360 degrees and had almost completed a second circle when it was lost off radar. The last recorded altitude was 800 feet, the airplane subsequently descended into the terrain with no warning provided by ATC.
Probable cause
The pilots failure to maintain his assigned altitude in IFR conditions. A related factor was the failure of the radar controller to prevent the descent of N2881W to an altitude below the minimum vectoring altitude. Additionally, the controller's failure to issue a safety alert after the MSAW issued 4 warnings in the radar room.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97FA001
- Event ID
- 20001208X06896
- Case number
- IAD97FA001
- 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: b24e75590564ca8861849d8624e55aada9a1504c9f945f04de4d0c7ca1a23b92; retrieved 2026-09-20T23:10:48.406Z.