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

May 17, 1995 · Rockwell 112B · N1409J

Edgewater, MD

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 17, 1995
Injury Outcomes
No injuries (2 uninjured)
Location
Edgewater, MD
Aircraft
Rockwell 112B
Tail Number
N1409J
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC95LA111

THE AIRPLANE LANDED ON A WET, NARROW 2500-FT RUNWAY. WHEN THE PILOT APPLIED THE BRAKES, THE AIRPLANE SKIDDED, DEPARTED THE RUNWAY, AND STRUCK A FENCE AND POLE. ACCORDING TO THE PILOT HE IMMEDIATELY APPLIED 'FULL BRAKES...BUT THERE WAS NIL SENSATION OF BRAKING EFFECT.' WITNESSES SAID IT WAS RAINING HEAVY, AND THE WINDS WERE GUSTING AND CHANGING DIRECTION. A WITNESS SAID THERE WERE 'STRONG GUSTING WINDS THAT WOULD BE A TAILWIND FOR LANDING ON RUNWAY 12.' ANOTHER WITNESS SAW THE AIRPLANE ON FINAL, AND '...IT WAS LINED UP FOR RUNWAY 12, APPEARED TO BE HIGH ON THE APPROACH AND FAST...[AND] APPEARED TO BE IN A CRAB....' THE NEAREST REPORTED WEATHER WAS AT BALTIMORE, ABOUT 14 NM NORTH OF THE ACCIDENT SITE. THE 1805 OBSERVATION WAS 1,700 BROKEN, 12,000 OVERCAST, VISIBILITY 7 MILES, THUNDERSTORMS AND LIGHT RAIN, WIND 260 DEG AT 9 KNOTS, GUSTING TO 21.

NTSB Probable Cause

THE PILOT'S IMPROPER DECISION TO CONTINUE HIS FLIGHT INTO THE ADVERSE WEATHER CONDITIONS THAT EXISTED AT THE DESTINATION AIRPORT. THE WEATHER CONTRIBUTED TO THE ACCIDENT.

Full Narrative

On May 17, 1995, about 1815 eastern daylight time, a Rockwell 112B, N1409J, was substantially damaged when it collided with a fence during the landing roll at Lee Airport, Edgewater, Maryland. The airline transport pilot and one passenger were not injured. Visual meteorological conditions prevailed, and an IFR flight plan had been filed. The personal flight departed Chesapeake, Virginia at 1645, and was conducted under 14 CFR Part 91. The airplane landed on runway 12 (2500 feet long and 45 feet wide). The runway was wet, and when the pilot applied the brakes, the airplane skidded, departed the runway, struck a fence, and a pole. The pilot stated that he had departed a day earlier, "...so as not to rush and avoid bad forecasted weather." He filed an IFR flight plan with Leesburg Flight Service Station (FSS), and received a full weather briefing. He wrote, "...FSS commented weather was not unfolding as badly as predicted." En route at 7000 feet mean sea level (MSL), the pilot stated he was "in and out of the clouds [and] noticed strong winds from the west...." According to the pilot's statement on the NTSB Form 6120.1/2: ...on let down...altitude 2500 feet and vectors to Lee, controller said he had no landing weather at Lee, but that his radar did show some rain over the field when we were about 15 miles out. He also said there was a convective SIGMET to the north closer to Baltimore...we had good visual contact with [the] ground at 2500 feet. and 3 miles visibility, so we proceeded to the field to checkout the field (winds, aircraft on runway etc.). We had good visual contact with the field. The rain was aligned to the runway but to the north of the field, south of the field it was clear with no rain and even the sun breaking out in [the] distance about 25-30 miles estimate. We made three calls on Lee UNICOM 122.4 for advisories but got no reply. The pilot cancelled his IFR flight plan and elected to approach the airport from the south and land on runway 12. According to the pilot he "calculated about 22 knots [wind] from the southeast." According to the pilot's statement: ...we then departed the field to the south to stay in the clear...we made another advisory call in the blind that we were approaching from the south...we rolled onto final on centerline and on VASI glideslope and experienced light rain, but no wind gusts air smooth. We touched down at displaced threshold at approximately 60 knots to 65 knots...told my son to raise the flaps to put more weight on the wheels for braking and directional control. I immediately applied full brakes...but there was nil sensation of braking effect. I then attempted to pump the brakes as in a manual anti-skid procedure and was as though we were skidding on ice. When I realized stopping on the runway was impossible, I put in full left rudder to avoid a building structure on the right at the end of the runway...we slid off the runway penetrated a cyclone fence and two poles at the end the end of the airport fence line, struck evergreen shrubs and one 4x4 posted sign...port [left] wing tip hit the upcoming bank building...turned 90 degrees or perpendicular to the building and came to a stop nose down.... The FAA inspector wrote: He [pilot] felt there were no conditions at any point in the approach and landing that he could not handle or would exceed the limitations of the aircraft. He said he had done this type of landing before in...military aircraft and this landing wasn't any different in his view. The FAA asked the pilot about wind shifts or possible tail winds, and the pilot responded, "he did not feel any." Witnesses that either saw the landing or the approach said at the time of the accident it was raining "heavy." The witnesses told the FAA the winds were gusting and changing direction. A witnesses told the FAA she saw the landing, and there were "strong gusting winds that would be a tail wind for landing on Runway 12..." One of the witnesses, an airline captain, saw the airplane on final approach. He wrote, "...it was lined up for runway 12, appeared to be high on the approach and fast...[and] appeared to be in a crab...." The nearest reported weather was at Baltimore (BWI) located about 14 nautical miles north of the accident site. The BWI 1805 weather observation was; 1700 broken, 12,000 overcast, visibility 7 miles, thunderstorms and light rain, temperature missing, dew point missing, wind 260 degrees, 9 knots, gusts to 21, altimeter 29.64 inches Hg.

Flight

Event TypeAccident
Event Time18:15 EDT
Nearest AirportLEE (0nm)
Runway12
Runway Length2500 ft
Runway Width45 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftRockwell 112B
Tail NumberN1409J
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-C1D6 · Reciprocating · 200
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 9 kt, gusting 21 kt
Visibility7 sm
CeilingBroken clouds 1700 ft
Temperature / Dew Point0 C / 0 C
Altimeter30.00 inHg
Observation Time22:05
Weather SourceWFAC

Appendix: Source Data