Piper PA 28 N32582
24 August 2013 · Tehachapi, California, United States · Serious injuries
Summary
On 24 August 2013 at about 23:30 local time, a Piper PA 28 registered N32582 was involved in an accident near Tehachapi, California, United States. 3 people were on board and one was seriously injured, 2 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:30
- Classification
- Accident
- Location
- Tehachapi, California, United States
- Nearest airport
- Mountain Valley (L94)
- Coordinates
- 35.1011, -118.4231
- Aircraft
- Piper PA 28
- Registration
- N32582
- Category
- Airplane
- Year built
- 1974
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Tehachapi → Fullerton
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR13FA386
People
1 person was seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 0 | 1 | 2 | 0 |
Probable cause
The pilot's failure to conduct predeparture airplane performance planning for a departure from a high density altitude location, which resulted in his selection of a flightpath toward rising terrain that the airplane was not capable of outclimbing.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot/owner based the single-engine airplane at an airport that was on flat terrain at an elevation of about 100 ft mean sea level (msl). He flew to another airport that was located near the perimeter of the southeast quadrant of a geographic bowl at an elevation of 4,220 ft msl. The pilot had not previously flown into or out of the destination airport and had only flown one time into and out of a high-elevation airport (about 6,700 ft msl). The flight to the destination was uneventful. Later that afternoon, the pilot performed a weight-and-balance check and obtained a weather briefing before departure for the trip home. He did not conduct any density altitude, takeoff, or climb performance calculations. The pilot reported that the takeoff roll and initial climbout were normal, but when he turned onto the left crosswind leg, the airplane no longer seemed to be climbing. The airplane struck terrain about ½ mile from the departure end of the runway. The impact location elevation was about 160 ft above the departure airport elevation. Examination of the airplane, engine, and propeller did not reveal any preexisting mechanical deficiencies or problems that would have precluded normal operation. Based on the calculated density altitude of about 6,700 ft, the airplane manufacturer's performance charts indicated that the airplane would require about 3,300 ft to attain an altitude of 50 ft above ground level (agl). The expected initial climb rate was about 310 ft per minute; without any wind or performance decrements, the airplane would have been about 115 ft agl when it reached the impact location. Performance decrements included loss of lift in the turn; possible less-than-ideal airframe, engine, propeller, or pilot performance; and adverse wind, including downdrafts and the loss of the headwind component during the turn. The departure airport was equipped with two parallel runways and no air traffic control tower. A dedicated traffic advisory radio frequency and opposite-direction traffic patterns were used to separate the airport's sailplane and powered airplane operations. In keeping with the airport's procedures, the pilot used runway 27L and attempted to fly a left traffic pattern for departure. Review of the local topography revealed that the terrain south of the airport rose relatively rapidly, while the terrain both west and north remained about the airport elevation for several miles. Had the pilot conducted predeparture climb performance calculations, he would have determined that the airplane's climb capability was significantly reduced by the high density altitude. That, in turn, should have prompted him to select a departure path that remained clear of rising terrain. Two available options included a straight-out departure from runway 27L or a right turn from either runway 27L or 27R once the pilot was assured that a right turnout would not create a traffic conflict with the sailplanes using the airport.
Quoted verbatim from the NTSB record.
Other Piper PA-28 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 9 Feb 2013 | Piper PA-28-140 | Sunnyside, Washington, United States | John Gilman | Minor injuries | - |
| 8 Jun 2013 | Piper PA-28-140 | Mosca, Colorado, United States | - | Fatal | 2 |
| 14 Oct 2013 | Piper PA 28-150 | Newport, New Hampshire, United States | Bret Lukezic | No injuries | - |
| 2 Oct 2013 | Piper PA 28-180 | Benton Harbor, Michigan, United States | - | Minor injuries | - |
| 27 Jul 2013 | Piper PA-28-181 | Columbus, Georgia, United States | - | No injuries | - |
| 9 Nov 2013 | Piper PA 28-150 | Concordia, Kansas, United States | Link Gerald L | No injuries | - |
All 9,402 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Feb 2013 | Bell 206B | Acton, California, United States | Orbic Air | Fatal | 3 |
| 10 Feb 2013 | Bell 206B | Shandon, California, United States | Sycan Corp DBA | No injuries | - |
| 9 Sep 2013 | Grumman American Avn AA 1C | Hemet, California, United States | William Ralph Eddings | Minor injuries | - |
| 12 Feb 2013 | St Clair LANCAIR 360 | Williams, California, United States | - | Serious injuries | - |
| 14 Feb 2013 | Avions Fairey TIPSY NIPPER T-66 | Winters, California, United States | Sharman Enterprises Inc | Fatal | 1 |
| 9 Sep 2013 | Cessna 172N | Long Beach, California, United States | - | No injuries | - |