Skip to content

Atlas / NTSB / NYC99LA191

NTSB CAROL · Event

Event NYC99LA191

1999-08-01 FREDERICK, Maryland, United States Airport · FDK None 1 aircraft Status: Completed

Registry · N70894

FAA Aircraft Registry record.

Make / Model

PIPER J3C-65

Year of manufacture

1946 · 53 years old at event

Engine

CONT MOTOR A&C65 SERIES (65 hp)

Seats / Engines

2 seats · 1 engine

Last airworthiness date

19560710

ADS-B equipped

Yes — Mode-S A975F6

Registrant of record

SANDERS WILLIAM H

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to maintain directional control. Contributing factors were gusty wind conditions and the sign.

Factual narrative

On August 1, 1999, at 1440 eastern daylight time, a Piper J3C-65, N70894, was substantially damage during landing, when it departed the right side of runway 23 at Frederick Municipal Airport, Frederick, Maryland. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed for the personal flight that originated from Haysfield Airport, Clarksville, Maryland. A visual flight rules flight plan was filed, and the flight was conducted under 14 CFR Part 91. According to the Pilot/Operator Aircraft Accident Report Form, the pilot obtained a standard weather briefing, and then filed a flight plan. He then received a weather update from flight service approximately 5 minutes before executing the flight. During the update, the briefer indicated that scattered thunderstorms in the Hagerstown, Maryland area were moving east towards Frederick. The pilot calculated that he would arrive at his destination prior to the thunderstorms, so he departed Haysfield. While approaching his destination, the pilot noticed the sky to the north of his position was "very dark." He also experienced an increase in turbulence. The pilot checked weather with Frederick UNICOM, and was advised the winds were 4 knots. With the approaching thunderstorms, the pilot expedited his turn from base to final for runway 23. He then executed a "normal" landing. As the airplane was rolling out it became airborne and started to drift to the right. The airplane touched down, exited the runway, and the landing gear collapsed when it struck a sign. The pilot shut off both magnetos, secured the throttle, and exited the airplane. The pilot added, "I think I encountered a gust and simply lost control." The pilot obtained a standard weather briefing, and then filed a flight plan. He then received a weather update from flight service approximately 5 minutes before executing the flight. During the update, the briefer indicated that scattered thunderstorms in the Hagerstown area were moving east towards Frederick. The pilot calculated that he would arrive at his destination prior to the thunderstorms, so he departed. While approaching his destination, the pilot noticed the sky to the north of his position was 'very dark.' He also experienced an increase in turbulence. The pilot checked weather with Frederick UNICOM, and was advised the winds were 4 knots. With the approaching thunderstorms, the pilot expedited his turn from base to final, and executed a 'normal' landing. As the airplane rolled out it became airborne and started to drift to the right. The airplane touched down, exited the runway, and the landing gear collapsed when it struck a sign. The pilot shut off both magnetos, secured the throttle, and exited the airplane. The pilot stated, 'I think I encountered a gust and simply lost control.' Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_1999_NYC99LA191.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (turbulence, thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗