Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 3, 1999 · Piper PA-60-700P · N407SA

Greenville, ME

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 3, 1999
Injury Outcomes
No injuries (2 uninjured)
Location
Greenville, ME
Aircraft
Piper PA-60-700P
Tail Number
N407SA
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC00LA003

After entering VFR conditions at 6,000 feet MSL, the pilot canceled his IFR flight plan and made a straight-in, visual approach to a Runway 14, which had been NOTAM'd closed. During the landing, the airplane struck a lighted barricade and it's left wing contacted a 5 to 6 foot high pile of gravel located about 3,100 feet beyond the approach end of the runway. The pilot stated he re-checked the NOTAMS for the airport after the accident, and observed the NOTAM for the closed runway. The pilot said it was possible that he did not scroll all the way down the computer screen when he originally checked the NOTAMS.

NTSB Probable Cause

The pilot's inadequate preflight planning and his inadequate visual lookout.

Full Narrative

On October 3, 1999, about 1215 Eastern Daylight Time, a Piper PA-60-700P, N407SA, was substantially damaged while landing at the Greenville Municipal Airport (3B1), Greenville, Maine. The certificated commercial pilot and passenger were not injured. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan had been filed for the flight that departed the Laurence G. Hanscom Airport, Bedford, Massachusetts, about 1115. The personal flight was conducted under 14 CFR Part 91. The Greenville Municipal Airport was serviced by two runways. Runway 03/21, and Runway 14/32. At the time of the accident, runway 14/32 was closed, and a Notice To Airmen (NOTAM) had been issued. In a written statement, the pilot said he obtained a weather briefing and reviewed NOTAMS before the flight using "Destination Direct Flight Planning Software" and he did not see the NOTAM for 3B1. Approximately 20 minutes before landing, he checked the weather at Bangor (BGR), Maine, and planned to land on runway 14, a 3,999 foot long, 75 foot wide, asphalt runway. The pilot descended to 6,000 feet MSL, where he entered visual flight rules (VFR) conditions. The pilot then cancelled his IFR clearance and made a straight-in, visual approach to the runway, utilizing the Precision Approach Path Indicator (PAPI) lights, which were operational. The pilot further stated: "...The aircraft passed over the numbers and touched down approximately 500 to 600 feet from the approach end of the runway. I was not able to see any of the construction due to the significant crown to the runway, so I began normal braking. Upon reaching the crown in the runway, I observed debris [on] the runway, and immediately applied maximum braking. The wheels locked up and it became apparent that the plane could not be stopped prior to reaching the debris...." The airplane struck a lighted barricade and it's left wing contacted a 5 to 6 foot high pile of gravel located about 3,100 feet beyond the approach end of Runway 14. Examination of the accident site by a Federal Aviation Administration Inspector (FAA), revealed that an orange colored "X" had been placed on the approach end of Runway 32. There were no markings present on the approach end of Runway 14. In an interview with an FAA Inspector, the pilot stated he re-checked the NOTAMS for 3B1 after the accident, and observed the NOTAM for the closed runway. The pilot said it was possible that he did not scroll all the way down the computer screen when he originally checked the NOTAMS. Winds reported at BGR, which was located about 50 miles southeast of the accident site, at 1153, were from 210 degrees, at 4 knots.

Flight

Event TypeAccident
Event Time12:15 EDT
Nearest AirportGreenville Muni (0nm)
Runway14
Runway Length3999 ft
Runway Width75 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-60-700P
Tail NumberN407SA
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540 · Reciprocating · 350
Seats6

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 41 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 4 kt
Visibility10 sm
CeilingOvercast 9000 ft
Temperature / Dew Point61 F / 55
Altimeter30.00 inHg
Observation Time15:53
Weather SourceWFAC

Appendix: Source Data