# Accident 20061019021519A: Piper PA46310P, Fort Meade, MD, October 19, 2006

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 19, 2006, 15:43 local time
- Place: Fort Meade, MD
- Airport: Tipton Apt
- Damage: Destroyed
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 39.0850° N, 76.7464° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.0850&lon=-76.7464&mi=10
- Aircraft: N9130N, a cancelled registration (https://openairdocs.org/deregistered/N9130N-2018-01-29) (OpenAirDocs)
- Registry model: Piper PA-46-310P (registry code 7104605, https://openairdocs.org/model/piper-pa-46-310p) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: PIPER PA46310P
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 3,800 total
- NTSB investigation: [NTSB NYC07FA009](https://openairdocs.org/ntsb/NYC07FA009) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20061019021519A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT DEPARTED FME, VFR, TRANSPONDER CODE 1200. UPON CONTACTING PTC, THE PILOT WAS INSTRUCTED THAT HE WAS IN VIOLATION OF ADIZ AIRSPACE PROCEDURES AND INSTRUCTED TO LAND IMMEDIATELY AT FME. PILOT APPEARS TO HAVE OVER-SHOT FINAL APPROACH TO RUNWAY 28 @ FME AND OVER-BANKED AIRCRAFT RESULTING IN A POSSIBLE STALL AT LOW-LEVEL, RESULTING IN THE AIRCRAFT CRASHING INTO A WOODED AREA EAST OF CENTERLINE OF RUNWAY 28. THE PILOT AND PASSENGER WERE KILLED AND A FIRE RESULTED, TOTALLY DESTROYING THE AIRCRAFT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC07FA009](https://openairdocs.org/ntsb/NYC07FA009), Oct 19, 2006: Piper PA-46-310P (N9130N), Odenton, MD, destroyed, 2 fatal. Probable cause: The pilot's failure to maintain adequate clearance from terrain during the approach. Contributing was the pilot's self-induced pressure to land the airplane after being informed by air traffic…

## Other reports on N9130N (2)

Matched to the same aircraft by N-number and date.

- [Incident 20010815023809I](https://openairdocs.org/incident/20010815023809I), Aug 15, 2001: Piper PA46310P (N9130N), Cocoa, FL, Minor damage. (-23) During night landing, pilot attempted to command airport runway lights on by clicking his mike button on the assigned radio frequency. The runway lights…
- [Accident 19960823024079A](https://openairdocs.org/incident/19960823024079A), Aug 23, 1996: Piper PA46310P (N9130N), Redlands, CA, Substantial damage. Took off to avoid thunderstorm west. Settled on climbout. Hit prop. Aborted. Ran off into rocks. Variable gusts.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.