# Accident 20020613012209A: Piper PA32R300, Beaumont, KS, June 13, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 13, 2002, 10:00 local time
- Place: Beaumont, KS
- Airport: Beaumont Hotel Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 37.6698° N, 96.5506° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.6698&lon=-96.5506&mi=10
- Aircraft: N38709, a cancelled registration (https://openairdocs.org/deregistered/N38709-2003-07-09) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- NTSB investigation: [NTSB CHI02LA162](https://openairdocs.org/ntsb/CHI02LA162) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020613012209A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE PILOT ATTEMPTED A DOWNHILL SOUTH TAKEOFF ON THE 2200 FEET NORTH/SOUTH PRIVATE RUNWAY OF THE BEAUMONT HOTEL, BEAUMONT, KS. RUNWAY CONDITIONS AT THE TIME OF THE ATTEMPTED TAKEOFF WAS 2 TO 3 INCHES OF WET GRASS AND MOIST BUT MOSTLY FIRM GROUND. PILOT STATEMENTS AND PHYSICAL EVIDENCE INDICATE THAT DURING THE TAKEOFF RUN THE AIRCRAFT ENCOUNTERED A SOFTER RUNWAY SURFACE AFTER APPROXIMATELY 70%-75% OF THE RUNWAY LENGTH (APPROX 600 FEET REMAINING). THE AIRCRAFT BEGAN TO VEER LEFT SLIGHTLY AS THE LEFT MAIN WHEEL BEGAN CREATING A 1 INCH RUT. THE RUTTING OF THE LEFT MAIN WHEEL CONTINUED FOR APPROXIMATELY 500 FEET. THE AIRCRAFT FAILED TO ATTAIN FLYING SPEED BY THE END OF THE RUNWAY CONTINUING THROUGH 150 FEET OF UNMOWED GRASS IN THE OVER RUN (8 TO 10 INCHES HIGH), THEN ENCOUNTERED SOME BUSHES AND A 6 TO 8 INCH DIAMETER TREE, SEPARATING THE LEFT WING FROM THE FUSELAGE. THE AIRCRAFT CONTINUED AN ADDITIONAL 150 FEET AND CAME TO REST ON THE NORTH FACE OF AN ABANDONED RAILROAD BED EMBANKMENT. THE AIRCRAFT SUFFERED SUBSTANTIAL DAMAGE TO THE FUSELAGE, EMPENNAGE, WINGS, AND PROPELLER. THERE WAS NO POST ACCIDENT FIRE AD THE OCCUPANTS SUFFERED NO INJURIES.                                      (.19) ON JUNE 13, 2002, AT 1000 CENTRAL DAYLIGHT TIME, A PIPER PA-32, N38709, PILOTED BY A PRIVATE PILOT WAS DESTROYED FOLLOWING IMPACT WITH TREES ON TAKEOFF ROLL FROM THE RUNWAY AT THE SUMMIT HOUSE AIRPORT (SN07), BEAUMONT, KANSAS. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME OF THE ACCIDENT. THE 14 CFR PART 91 PERSONAL FLIGHT WAS NOT OPERATING ON A FLIGHT PLAN. THE PILOT AND TWO PASSENGERS WERE UNINJURED. THE FLIGHT WAS ORIGINATING AT THE TIME OF THE ACCIDENT AND WAS EN ROUTE TO EUREKA MUNICIPAL AIRPORT (13K), EUREKA, KANSAS.

## 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 CHI02LA162](https://openairdocs.org/ntsb/CHI02LA162), Jun 13, 2002: Piper PA-32R-300 (N38709), Beaumont, KS, substantial damage. Probable cause: The pilot's inadequate preflight planning and his failure to abort the takeoff when he realized the aircraft was not accelerating as expected. The wet and muddy turf runway was a contributing factor.

## Other reports on N38709 (1)

Matched to the same aircraft by N-number and date.

- [Incident 19940113001689I](https://openairdocs.org/incident/19940113001689I), Jan 13, 1994: Piper PA32R300 (N38709), Jackson, TN, Minor damage. Narrative: jan 13, 1994, at 1728 local CDT PA-32-300R Piper lance N38079 was taxiing out on the new ramp at mkl (Jackson, TN) following comp. Traffic when it…

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.
