# Accident 20101017048009A: Piper PA-28-140, Derby, KS, October 17, 2010 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: October 17, 2010, 08:35 local time - Place: Derby, KS - Damage: Substantial damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 37.5664° N, 97.1744° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=37.5664&lon=-97.1744&mi=10 - Aircraft: N8038N, a cancelled registration (https://openairdocs.org/deregistered/N8038N-2011-01-31) (OpenAirDocs) - Registry model: Piper PA-28-140 (registry code 7102802, https://openairdocs.org/model/piper-pa-28-140) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: PIPER PA-28-140 - Reported engine: LYCOMING 0-320 SERIES - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 301 total, 255 in this make and model, 15 in the last 90 days - NTSB investigation: [NTSB CEN11CA032](https://openairdocs.org/ntsb/CEN11CA032) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20101017048009A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON OCTOBER 17TH, 2010, AT APPROXIMATELY 0835 LOCAL TIME (1335 UTC), A PRIVATE PILOT WAS INVOLVED IN AN AIRCRAFT ACCIDENT RESULTING FROM THE AIRCRAFT EXITING THE RUNWAY SURFACE DURING ROLL-OUT AFTER LANDING AT THE DERBY-COOK AIRPORT (K50), DERBY, KANSAS. THE AIRCRAFT INVOLVED IN THE ACCIDENT IS A PIPER PA-28-140 AIRCRAFT, WHICH IS OWNED AND OPERATED BY THE PILOT-IN-COMMAND. VISUAL METEOROLOGICAL CONDITIONS (VMC) PREVAILED AT THE TIME OF THE ACCIDENT; JABARA AIRPORT (KAAO) AUTOMATED SURFACE OBSERVATION SYSTEM (ASOS) WAS REPORTING THE WINDS AS 020 DEGREES AT 4 KNOTS. THE AIRMAN REPORTED THE WINDS AT THE DERBY-COOK AIRPORT TO BE LIGHT AND VARIABLE, FAVORING A LANDING ON RUNWAY 35. UPON BEING ESTABLISHED ON FINAL FOR RUNWAY 35 AND CONFIGURED FOR LANDING WITH 20 DEGREES OF APPROACH FLAP, THE AIRMAN NOTED THAT THE AIRCRAFT WAS FLYING APPROXIMATELY 5-10 MPH FASTER THAN NORMAL. THE AIRCRAFT'S APPROXIMATE AIRSPEED ON FINAL WAS 90 MPH; THE AIRMAN INDICATED THAT THE NORMAL LANDING CONFIGURATION AND SPEED WOULD BE 20 DEGREES OF FLAPS AND 80 MPH. PER THE AIRMAN, DURING THE LANDING PHASE, THE AIRCRAFT BALLOONED AND FLOATED, AND SUBSEQUENTLY LANDED JUST PRIOR TO THE MID-POINT OF RUNWAY 35; RUNWAY 17/35 IS 2,507 FT IN LENGTH AND 40 FT IN WIDTH. UPON TOUCHDOWN, THE AIRMAN STATED THAT MAXIMUM BRAKING WAS APPLIED AS THE AIRCRAFT WAS QUICKLY APPROACHING THE END OF THE RUNWAY. DUE TO THE EXCESSIVE SPEED, THE AIRMAN WAS UNABLE TO STOP THE AIRCRAFT PRIOR TO ITS DEPARTURE FROM THE RUNWAY SURFACE. PER THE AIRMAN, A GO-AROUND WAS NOT ATTEMPTED AT ANY TIME. PRIOR TO THE AIRCRAFT EXITING THE RUNWAY, THE AIRCRAFT BEGAN VEERING RIGHT OF CENTERLINE; EXCESSIVE BRAKING CAUSED A PERFORATION IN THE RIGHT TIRE EXACERBATING THE AIRCRAFT'S DEPARTURE FROM RUNWAY CENTERLINE. THE AIRCRAFT SUBSEQUENTLY ROLLED DOWN A SMALL EMBANKMENT AT THE END OF THE RUNWAY AND IMPACTED AN AIRPORT BOUNDARY BARRIER CONSISTING OF HORIZONTALLY LAID TELEPHONE POLES AND CONCRETE CYLINDERS. UPON IMPACT, THE AIRCRAFT'S RIGHT MAIN GEAR AND NOSE WHEEL WERE SHEERED OFF; THE LEFT MAIN WHEEL WAS ATTACHED TO THE AIRCRAFT BY A BRAKE LINE ONLY. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE TO THE ENGINE FIREWALL AS A DIRECT RESULT OF IT IMPACTING THE AIRPORT BOUNDARY BARRIER. NO INJURIES WERE REPORTED BY EITHER THE AIRMAN OR PASSENGER. ## The NTSB's investigation of this event (1) 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. - [NTSB CEN11CA032](https://openairdocs.org/ntsb/CEN11CA032), Oct 17, 2010: Piper PA-28-140 (N8038N), Rose Hill, KS, substantial damage. Probable cause: The pilot's improper touchdown point during landing, which resulted in a runway overrun. ## Other reports on N8038N (1) Matched to the same aircraft by N-number and date. - [Accident 19770623019549A](https://openairdocs.org/incident/19770623019549A), Jun 23, 1977: Piper PA28140 (N8038N), Colo Springs, CO, Substantial damage. Un estab pos climb rate. Hit arpt boundary fence. Overweight 110LB.dens alt 8000FT. From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- 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.