FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC07LA206 · Piper PA-28-181

30 Aug 2007 · Sevierville, TN, United States

Piper PA-28-181 · Accident: overrun during landing

From Scott Municipal Airport (SCX) to Seymour Air Park (TN20)

Report a problem

Event

NTSB case
NYC07LA206
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-181

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3077Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Scott Municipal Airport (SCX), Oneida, TNTo Seymour Air Park (TN20), Seymour, TN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Distance/speed, misjudged

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the Piper PA-28 cancelled his instrument flight rules clearance and descended for a visual flight rules approach to the 2,300-foot -long turf airstrip, where he knew it had previously rained. He conducted a low pass along the runway to determine airport conditions. He observed the wind sock to be "limp," and did not see any standing water on the runway. He completed another circuit of the traffic pattern and flew a "stable approach" using full flaps. The pilot stated that on final approach he had a "normal sight picture...with sufficient runway for normal ground roll," and that touchdown occurred with 1,500 feet of runway remaining. After touchdown, the pilot recognized the reduced braking effectiveness due to the wet grass, and applied heavy braking. The airplane overran the runway, crossed a road, and impacted trees. For a dry paved runway, the landing performance charts in the Pilot Operating Handbook (POH) indicated a total landing distance of approximately 1,300 feet, which included a ground roll of approximately 800 feet. The POH did not contain any qualitative or quantitative landing distance information for turf, wet, or wet turf runways.

Probable cause

The pilot misjudged his speed and distance resulting in an overrun. Contributing to the accident was the wet turf runway and the lack of any information in the pilot operating handbook regarding landing distance on a wet turf runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC07LA206
Event ID
20080321X00347
Case number
NYC07LA206
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 5177e0a6f2739ba14aceea902681b5bd52cd9b0144a6d52e7edd112cd76ec2c7; retrieved 2026-09-22T03:28:56.535Z.