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

January 14, 2002 · Piper PA-28-180 · N3997R

Oxford, MA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 14, 2002
Injury Outcomes
1 injury (1 minor injury)
Location
Oxford, MA
Aircraft
Piper PA-28-180
Tail Number
N3997R
Operator
Eagle East Aviation
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
IAD02LA025

The pilot was on a cross country flight when he became disoriented and misidentified the airport that he intended to land at with another airport located about 9 miles away. Both airports had the same runway alignment and Unicom frequency. The pilot performed a short field approach to runway 02, and landed about 1/3 of the way down the 2,097 foot long snow and patchy ice covered runway. He said that he "landed longer down the runway than he would have liked, and that was part of the problem." During the landing roll-out, the pilot said that he avoided hard braking due to the runway conditions. As the airplane came over a rise, he noticed a snow bank located at the end of the runway and decided to abort the landing. With less than half of the runway length available, the pilot applied power and tried to establish a climb, but was unable to clear the trees. The pilot reported that there were no mechanical deficiencies. He also reported that the accident could have been prevented by, "strict adherence to the flight plan...use of multiple characteristics to identify rural airports...[and] more precise execution of short-field procedure." A review of the Piper PA-28-180 takeoff performance charts revealed that the airplane would have needed approximately 1,625 feet to take off over a 50-foot obstacle on a paved, level, dry runway in zero wind conditions with 25 degrees of flaps extended, and full power applied before brake release.

NTSB Probable Cause

The pilot's delayed aborted landing and his failure to attain obstacle clearance. The pilot's misjudgment of distance is a contributing factor.

Full Narrative

On January 14, 2002, at 1210 eastern standard time, a Piper PA-28-180, N3997R, was substantially damaged during an aborted landing at Oxford Airport (43M), Oxford, Massachusetts. The certificated private pilot sustained minor injuries. Visual meteorological conditions prevailed for the flight that originated at Lawrence Municipal Airport (LWM), Lawrence, Massachusetts, about 1130. A visual flight rules flight plan was filed for the business flight conducted under 14 CFR Part 91. The pilot's intended destination was the Southbridge Municipal Airport (3B0), Southbridge, Massachusetts, which was located about 9.5 miles southwest of the Oxford Airport. Prior to his departure, he contacted the fixed base operator at Southbridge Airport to "assure that the runway was cleared of the recent snowfall and ascertain the local winds." The pilot reported that he had prepared an index card with Southbridge Municipal Airport's information as part of his pre-flight planning, and carried an aeronautical sectional chart on board the airplane during the flight. He also said that he owned an airport facility directory (AFD). As the pilot approached the area of his intended destination, he contacted the Southbridge Airport Unicom and requested airport advisories. He was informed by an airport operator that runway 02 was in use. The pilot said that he then became disoriented and misidentified the Oxford Airport as the Southbridge Municipal Airport. In a written statement, the pilot said: "I approached the [Oxford] airport. I assumed that this was the Southbridge Airport. I inspected the runway finding no other traffic. I radioed my landing intentions and I proceeded to land the aircraft." "When it appeared that I could not stop prior to reaching the end of the runway, I advanced the power in order to take-off again for a second approach. During the take-off, the aircraft could not gain enough altitude to clear the trees that are located at the north end of the runway. The right wing of the aircraft encountered the trees causing the aircraft to rotate to the right, nosed over settling though the trees, landing inverted." In a telephone conversation, the pilot said that he configured the airplane for a short field landing on runway 02. He utilized full flaps and stabilized airspeed. The pilot reported that there were 30-40 foot tall trees at the approach end of the runway, that he had not anticipated, and noted that the wind sock indicated calm winds. The pilot stated that he landed about 1/3 of the way down the runway, which "was longer down the runway than he would have liked, and that was part of the problem." The pilot said that during the landing roll out, he "avoided hard braking due to the runway conditions," which he described as "snow, patchy ice." As the airplane came over a rise, the pilot noticed a snow bank located at the end of the runway and decided to abort the landing. With less than half of the runway length available, he applied power and tried to establish a climb, but was unable to clear the trees. The pilot held a private pilot certificate with a rating for airplane single engine land. He reported a total of 156 flight hours, of which 37 hours were in make and model. The pilot reported that there were no mechanical deficiencies with the airplane or engine. Oxford Airport was an uncontrolled airport with a Unicom/common traffic advisory frequency (CTAF) of 122.8. The airport had one runway, which was aligned 02/20. It was a 2,047 foot long and 50 foot wide asphalt runway with 52 foot high trees located at the approach end of runway 02, and 36 foot high trees located at the approach end of runway 20. Southbridge Municipal Airport was also an uncontrolled airport with a Unicom/CTAF of 122.8. The airport had two runways, which were aligned 02/20 and 10/28. Runway 02/20 was an asphalt runway that was 3,500 feet long and 75 feet wide. Runway 10/28 was a turf runway that was 1,450 feet long and 100 feet wide. A review of the Piper PA-28-180 Landing Distance and Takeoff performance chart revealed that with a paved, level, dry runway, with no wind, and maximum braking, the airplane at full gross weight required approximately 1,185 feet to land over a 50 foot high obstacle, and approximately 1,625 feet to take off over a 50 foot high obstacle from a paved, level, dry runway in zero wind conditions with 25 degree of flaps, and full power before brake release. Weather at Worcester Regional Airport, about 7 nautical miles to the north, at 1221, was reported as wind from 260 degrees at 7 knots gusting to 18 knots, winds variable between 240 and 300 degrees, visibility 10 statute miles, few clouds at 11,000 feet, temperature 42 degrees F, dewpoint 48 degrees F, and altimeter setting 30.02 inches HG. Additionally, the pilot said that the accident could have been prevented by, "strict adherence to the flight plan...use of multiple characteristics to identify rural airports...[and] more precise execution of short-field procedure."

Flight

Event TypeAccident
Event Time12:10 EST
Nearest AirportOXFORD (0nm)
Runway02
Runway Length2047 ft
Runway Width50 ft
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-180
Tail NumberN3997R
Aircraft CategoryAir
DamageSubstantial
OperatorEagle East Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4MCA4A · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 57 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 7 kt, gusting 18 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point34 C / 48
Altimeter30.02 inHg
Observation Time17:21
Weather SourceWFAC

Appendix: Source Data