NYC03LA125

NTSB accident investigation · Cessna 172L · Newburyport, MA · June 7, 2003

Accident · No injuriesLimited investigationFinal report
Date
June 7, 2003, 11:39 local (15:39 UTC)
Place
Newburyport, MA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7149QCessna 172L
Weather
Visual (VMC) · Day
Status
Completed · report April 28, 2004
Report
Approved by Office Director
Parties
FAA/FSDO
FAA report
20030607010999A
Case key
57164

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 attain the proper touchdown point.

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.

Loss of control - on ground/waterLanding - roll
Proper touchdown point - not attainedPilot in commandCause
On ground/water collision with objectLanding - roll
Object - fence

Analysis

The pilot stated he was "a little hot " during the landing, and as he applied the brakes, he initially received no response from the airplane. The right brake then "took hold" and the airplane veered to the right into the grass. The airplane continued through a fence at the end of the runway. Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed no mechanical anomalies. Additionally, skid marks were observed on the runway about half way down its length.

Factual narrative

On June 7, 2003, at 1139 eastern daylight time, a Cessna 172L, N7149Q, was substantially damaged during landing at Plum Island Airport (2B2), Newburyport, Massachusetts. The certificated private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 CFR Part 91.

According to the pilot, he made a left downwind entry to the traffic pattern for runway 10 at Plum Island. He stated that he touched down about 400 feet beyond the runway threshold of the 2,105 foot-long and 50 foot-wide runway. The pilot reported he was "a little hot " during the landing, and as he applied the brakes, he initially received no response from the airplane. The right brake then "took hold" and the airplane veered to the right into the grass. The airplane continued through a fence at the end of the runway.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed no mechanical anomalies. Additionally, skid marks were observed on the runway about half way down its length.

Weather reported at Lawrence Municipal Airport (LWM), Lawrence, Massachusetts, 13 miles from Plum Island, at 1054, included variable wind at 3 knots, 10 miles visibility, clear skies, temperature 70 degrees Fahrenheit, dew point 60 degrees Fahrenheit, and barometric pressure 29.99 inches Hg.

Aircraft

Registration
N7149Q
Reported as
Cessna 172L
Category
Airplane
Serial number
17260449
Airframe hours
3,710
Engine
Lycoming O-320, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Alex Hasapis
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 7, 2002 · 24 hours before
Departed
3B3 · Sterling, MA
Destination
2B2 · Newburyport, MA
Airport
2B2 · Plum Island Airport, runway 10, 2,105 × 50 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
71
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Last flight review
March 24, 2003
Seat
Left
Flight hours
330 total · 215 in this make and model · 14 in the last 90 days · 8 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
210° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
66 °F, dew point 63 °F
Altimeter
30.01 inHg
Observed at
LWM, 13 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.