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

March 30, 2014 · Beech S35 · N8985M

Marathon, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 30, 2014
Injury Outcomes
2 injuries (2 minor injuries)
Location
Marathon, FL
Aircraft
Beech S35 (1964)
Tail Number
N8985M
Operator
Tharp James R
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA14CA175

The pilot stated that after takeoff the flight proceeded IFR towards the destination airport (The Florida Keys Marathon Airport), Marathon, Florida. He cancelled his IFR clearance, and performed the pre-landing checklist. While on the base leg over water during the dark night, he became distracted by the failure of the landing light. With the landing gear and flaps extended for landing but the power set to 15 inches of manifold pressure, he did not recognize the airplane was descending. When the airplane impacted the water he thought they were at 1,000 feet. He also stated that he attempted to activate the runway lights using the common traffic advisory frequency but stated he could not see them. In hindsight he stated that he must have been too low at that time to see the runway lights. According to the County of Monroe Assistant Director of Airports, the runway lights at The Florida Keys Marathon Airport come on automatically at night and remain on "step 1." Being a 14 CFR Part 139 airport, a complete night inspection is performed each Friday and Monday, and each working day in the morning a continuous inspection is performed on the runway lighting circuit. As noted in the Daily Self Inspection Reports, the airfield runway lights were functioning properly during the course of the weekend and there were no issues with the runway lighting system. The runway end identifier lights for runway 7 were out of service at that time.

NTSB Probable Cause

The pilot's distraction in the cockpit while on a visual approach over water during a dark night resulting in the airplane descending until impact with the water.

Full Narrative

The pilot stated that after takeoff the flight proceeded IFR towards the destination airport (The Florida Keys Marathon Airport), Marathon, Florida. He cancelled his IFR clearance, and performed the pre-landing checklist. While on the base leg over water during the dark night, he became distracted by the failure of the landing light. With the landing gear and flaps extended for landing but the power set to 15 inches of manifold pressure, he did not recognize the airplane was descending. When the airplane impacted the water he thought they were at 1,000 feet. He also stated that he attempted to activate the runway lights using the common traffic advisory frequency but stated he could not see them. In hindsight he stated that he must have been too low at that time to see the runway lights.According to the County of Monroe Assistant Director of Airports, the runway lights at The Florida Keys Marathon Airport come on automatically at night and remain on "step 1." Being a 14 CFR Part 139 airport, a complete night inspection is performed each Friday and Monday, and each working day in the morning a continuous inspection is performed on the runway lighting circuit. As noted in the Daily Self Inspection Reports, the airfield runway lights were functioning properly during the course of the weekend and there were no issues with the runway lighting system. The runway end identifier lights for runway 7 were out of service at that time.

Flight

Event TypeAccident
Event Time20:17 EDT
Nearest AirportThe Florida Keys Marathon Arpt (3nm NE)
Runway25
Runway Length5008 ft
Runway Width100 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech S35
Tail NumberN8985M
Aircraft CategoryAir
DamageSubstantial
OperatorTharp James R
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · IO-520-B · Reciprocating · 285
Seats5

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 63 · Second Class · None

Conditions

ConditionsVMC
LightDark Night
WindCalm
Visibility10 sm
CeilingBroken clouds 9000 ft
Altimeter29.97 inHg
Observation Time23:53
Weather SourceWFAC

Appendix: Source Data