NTSB CAROL · Event
Event CEN13LA497
Registry · N727Y
FAA Aircraft Registry record.
Make / Model
PERTH AMBOY BIRD BK
Year of manufacture
1930 · 83 years old at event
Engine
KINNER K5 SERIES (100 hp)
Seats / Engines
3 seats · 1 engine
Last airworthiness date
20121022
ADS-B equipped
Yes — Mode-S A9BFB3
Registrant of record
NATIONAL AIR AND SPACE MUSEUM
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s loss of directional control during landing.
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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- — Environmental issues-Physical environment-Object/animal/substance-(general)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2013_CEN13LA497.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗