CEN13LA497

NTSB accident investigation · Perth Amboy Bird BK · Zanesville, OH · August 20, 2013

Accident · No injuriesLimited investigationFinal report
Date
August 20, 2013, 14:00 local (18:00 UTC)
Place
Zanesville, OH
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N727YPerth Amboy Bird BK
Defining event
Landing-landing roll: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report January 14, 2015
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA-Columbus FSDO
FAA report
20130820015079A
Case key
87825

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 loss of directional control during landing.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedPerth Amboy BIRD BK: 1 caseAll aircraft: 3,958 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotPerth Amboy BIRD BK: 1 caseAll aircraft: 9,295 casesProbable cause
Object/animal/substanceEnvironmental issues › Physical environment · Contributed to outcomePerth Amboy BIRD BK: 1 caseAll aircraft: 224 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that he intentionally taxied the airplane off the runway after landing to preserve the tires on the antique airplane due to a rough runway surface. The airplane subsequently encountered an unmarked drainage ditch. A postaccident examination showed that the airplane departed the right side of the runway about 150 feet from the approach end and traveled through a 40-foot-wide area of closely mowed grass, striking a runway light in the process. The airplane continued into an area of 1-foot-tall vegetation until it impacted the drainage ditch about 500 feet from the approach end of the runway. An examination of the runway did not reveal an excessively rough surface. The occurrence of the runway excursion within 150 feet of touching down and then the airplane traveling 500 feet after exiting the runway is consistent with airplane having significant speed at the time of the excursion, rather than an exit onto the grass under controlled conditions. The pilot likely lost directional control of the airplane during landing, which resulted in the airplane departing the runway, striking the runway light, and impacting into the ditch.

Factual narrative

On August 10, 2013 about 1400 eastern daylight time, a Perth Amboy, model BIRD BK, airplane, NC727Y, impacted terrain during a runway excursion after landing at the Parr Airport (42I), Zanesville, Ohio. The pilot was not injured. The airplane was substantially damaged. The airplane was registered to a private individual and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The flight originated from the Greater Cumberland Regional Airport, Cumberland, Maryland, about 1130.The pilot reported that after landing he noticed that the runway was rough, so he decided to exit the runway and taxi on the grass to preserve the tires on the antique airplane. Soon after leaving the runway, he encountered an unmarked drainage ditch, which the airplane went into. The airplane was an antique biplane and sustained damage to the fuselage, right main landing gear and both right wing spars. Runway 10 at 42I was a paved asphalt surface, 3,100 feet long and 26 feet wide. About 30 feet to either side of the runway's paved edge were rows of runway lights spaced about 100 feet apart. On the south side of the runway, the grass was mowed to a short height for about 40 feet from the south edge of the paved runway. South of this mowed area was an area of taller vegetation that was about 1 foot in height. Visible in the grass areas were tire tracks from the accident airplane which showed that it exited the south side of the runway about 150 feet from the approach end. The tracks proceeded through the short mowed grass area to where a broken runway light was at, and then continued into the taller vegetation. The tire tracks continued to a drainage ditch that was in the taller vegetation. The drainage ditch was about 500 feet from the approach end of the runway. Impact scars were visible near the ditch. Although the runway exhibited patched cracks in the pavement, it did not have a rough appearance.

Aircraft

Registration
N727Y
Reported as
Perth Amboy Bird BK (NO SERIES)
Category
Airplane
Serial number
2037-16
Built
1930
Engine
Kinner K5 SERIES, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · October 20, 2012
Departed
CBE · Cumberland, MD
Destination
42I · Zanesville, OH
Airport
42I · Parr Airport, runway 10, 3,100 × 26 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
53
Injuries
None
Certificate
Private
Airplane ratings
Single-engine sea, Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
June 20, 2012
Seat
Rear
Restraint
Lap only

Weather

Conditions
Visual (VMC) · Day
Wind
100° at 4 knots
Visibility
10 statute miles
Lowest ceiling
5,000 ft broken
Temperature
82 °F, dew point 59 °F
Altimeter
30.15 inHg
Observed at
ZZV, 6 nm away

Docket · 5

The files NTSB released with the investigation on December 16, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 14.1 MB in all.

FAA reports on this event · 1

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