# NTSB CEN10CA365: Piper PA-28-140, N643TP, Rogers, AR, June 28, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 28, 2010, 10:44 local (15:44 UTC) - Place: Rogers, AR - Coordinates: 36.372501, -94.106941 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.3725&lon=-94.1069&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 21, 2010 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 76507 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN10CA365 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76507/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76507 - Page: https://openairdocs.org/ntsb/CEN10CA365 ## Probable cause The pilot's failure to maintain a proper descent rate during the approach to land. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent rate](https://openairdocs.org/ntsb-findings/01062037): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-140, 2 cases](https://openairdocs.org/ntsb-findings/01062037/cases.md?model=7102802), [All aircraft, 242 cases](https://openairdocs.org/ntsb-findings/01062037/cases.md) - [Use of equip/info](https://openairdocs.org/ntsb-findings/02063000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-140, 1 case](https://openairdocs.org/ntsb-findings/02063000/cases.md?model=7102802), [All aircraft, 111 cases](https://openairdocs.org/ntsb-findings/02063000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Piper PA-28-140, 2 cases](https://openairdocs.org/ntsb-events/282/sequence.md?model=7102802), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md) - [Approach: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-28-140, 19 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7102802), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Piper PA-28-140, 11 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7102802), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The pilot stated that he was on short final when he noticed a higher-than-anticipated sink rate developing, so he added power. About 100 feet from the runway he became distracted by the stall warning light; the airplane landed short of the runway, bounced and struck the propeller before coming to a rest on the runway. Postaccident examination of the airplane revealed a bent firewall. The pilot indicated there was nothing wrong with the airplane prior to the accident. ## Factual narrative The pilot stated that he was on short final when he noticed a higher-than-anticipated sink rate developing, so he added power. About 100 feet from the runway he became distracted by the stall warning light; the airplane landed short of the runway, bounced and struck the propeller before coming to a rest on the runway. Postaccident examination of the airplane revealed a bent firewall. The pilot indicated there was nothing wrong with the airplane prior to the accident. ## Aircraft - Registration: [N643TP](https://openairdocs.org/aircraft/N643TP), registered now, S/N 28-7125176, built 1971 (OpenAirDocs) - Reported make and model: PIPER PA-28-140 - Registry model: [Piper PA-28-140](https://openairdocs.org/model/piper-pa-28-140) (registry code 7102802) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7125176 - Engines: Lycoming O-320 Series 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Unknown - Departed: SGF, Springfield, MO - Destination: ROG, Rogers, AR - Flight plan: Unknown - Airport: ROG, Rogers Municipal Airport, runway 02 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; flight hours: 146 total, 137 in this make and model, 109 as pilot in command, 7 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20100628035909A](https://openairdocs.org/incident/20100628035909A), Jun 28, 2010: Piper PA-28-140, Rogers, AR, Substantial damage. On June 28, 2010 at 1544Z during VMC conditions, the pilot was on short final to runway 2 at krog. He noticed he was a little short for the runway. He stated… ## Docket (2 files) The files NTSB released with the investigation on July 27, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76507. 505 KB in all. - FAA Email (Pilot Statement) (item 1, .PDF, 29 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333738&FileExtension=.PDF&FileName=FAA%20Email%20(Pilot%20Statement)-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 476 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333809&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.