NYC00LA041

NTSB accident investigation · Piper PA-28-161 · Annapolis, MD · November 29, 1999

Accident · No injuriesLimited investigationFinal report
Date
November 29, 1999, 12:20 local (17:20 UTC)
Place
Annapolis, MD
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8119PPiper PA-28-161
Weather
Visual (VMC) · Day
Status
Completed · report June 23, 2000
Report
Approved by Office Director
FAA report
19991129047439A
Case key
47892

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's failure to adequately adjust engine power to compensate for the winds on final approach.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

UndershootLanding
Weather condition - gusts
Compensation for wind conditions - inadequatePilot in commandCause
Go-around - not performedPilot in commandCause
On ground/water collision with objectLanding - roll

Analysis

The airplane was on a final approach, when the sink rate suddenly increased. The pilot applied more power, but the sink rate was not adequately arrested. The airplane hit a sign, rotated to the right, landed to the right of the runway, then collided with a chain link fence. Winds at the time were from 10 degrees to the left of the runway, at 18, gusting to 25 knots. The pilot's total flight time was about 125 hours.

Factual narrative

On November 29, 1999, about 1220 eastern standard time, a Piper PA-28-161, N8119P, was substantially damaged when it landed short of the runway at Lee Airport (ANP), Annapolis, Maryland. The certificated private pilot was uninjured, and visual meteorological conditions prevailed at the time of the accident. A visual flight rules flight plan was filed for the flight, from Salisbury-Ocean City Wicomico Regional Airport (SBY), Salisbury, Maryland, to Lee Airport. The flight was conducted under 14 CFR Part 91.

According to the pilot, he was on a final approach to Runway 30, at an airspeed of about 65 knots, with two notches of flaps selected. As he approached the runway, the airplane's sink rate increased. He applied more power, but the sink rate was not adequately arrested. The airplane hit a sign, rotated to the right, landed to the right of the runway, then collided with a chain link fence.

The pilot stated: "It is my conclusion that the wind suddenly eased, reducing airspeed and lift, allowing the plane to sink faster and hit the sign. I probably should have anticipated this, and made a steeper and faster approach...." The pilot had about 125 hours of flight time.

Weather at an airport 14 nautical miles to the north, about 25 minutes prior to the accident, included winds from 290 degrees magnetic, at 18, gusting to 25 knots.

Aircraft

Registration
N8119P
Reported as
Piper PA-28-161
Category
Airplane
Serial number
28-8016128
Airframe hours
8,919
Engine
Lycoming O-320, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Charles Deakyne
Registered owner
Navy Flying Club
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · November 8, 1999 · 46 hours before
Departed
SBY · Salisbury, MD
Destination
ANP
Airport
ANP · Lee Airport, runway 30, 2,505 × 48 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
72
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Seat
Left
Flight hours
126 total · 70 in this make and model · 106 as pilot in command · 19 in the last 90 days · 7 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
290° at 18 knots, gusting 25
Visibility
10 statute miles
Lowest ceiling
25,000 ft broken
Temperature
45 °F, dew point 39 °F
Altimeter
30.00 inHg
Observed at
BWI, 14 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.