Piper PA-22-135 N1540P
28 June 2013 · Yellow Pine, Idaho, United States · Fatal
Summary
On 28 June 2013 at about 15:48 local time, a Piper PA-22-135 registered N1540P, operated by Christopher Jordan, was involved in an accident near Yellow Pine, Idaho, United States. 4 people were on board and one died, 3 were seriously injured. 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 15:48
- Classification
- Accident
- Location
- Yellow Pine, Idaho, United States
- Nearest airport
- Johnson Creek Airport (3U2)
- Coordinates
- 44.9117, -115.4853
- Aircraft
- Piper PA-22-135
- Registration
- N1540P
- Category
- Airplane
- Engines
- 1
- Operator
- Christopher Jordan
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Salmon → Yellow Pine
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR13FA296
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 4 | 1 | 3 | 0 | 0 |
Probable cause
The other pilot’s failure to see and avoid the airplane, which resulted in a midair collision while both airplanes were on final approach to land. Contributing to the accident was both pilots’ failure to adequately monitor other aircraft position reports while in the pattern.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
A Piper PA-28R-200 and a Piper PA-22-135 collided while on short final approach to land at a nontowered remote airport. The PA-22-135 pilot reported that he made several position reports on the common traffic advisory frequency (CTAF) before performing an upwind entry to the airport traffic pattern from the north. He continued to turn the airplane to the crosswind, downwind, and base legs of the traffic pattern while announcing his positions on the CTAF and then turned the airplane to the final leg and again announced his position on the CTAF. The pilot stated that, as the airplane crossed the river north of the runway, he heard a transmission on the CTAF that "someone was too close" and that he began to abort the landing just before the collision occurred. The PA-28R-200 pilot reported that he initially approached the airport from the south, announced his position several times on the CTAF, and then entered the airport traffic pattern. However, he aborted his approach to land because an airplane was on the runway. The pilot then flew the airplane south to the vicinity of another airport for spacing from other airplanes in the area. He then proceeded to enter the airport traffic pattern a second time on an extended downwind while again announcing his position several times on the CTAF. The pilot stated that, while in the traffic pattern, he monitored his radio for the positions of other aircraft but that he heard no position reports indicating that an airplane was in front of his position or while he was on final approach. The pilot continued the approach to land and noted that the runway and the flightpath to the runway were clear. Shortly thereafter, the airplane collided with the PA-22-135. The pilot reported that he did not see the other airplane before the collision. A review of two videos of the collision revealed that the PA-28R-200 flew at a higher altitude than the PA-22-135 while on the downwind, base, and final legs of the airport traffic pattern. In addition, the videos showed that the PA-28R-200 overtook and then descended onto the PA-22-135. Given the PA-28R-200's descent angle and the position of the PA-22-135, it could not be determined if the PA-28R-200 pilot could have seen the PA-22-135. A review of the recorded CTAF transmissions revealed that both pilots were transmitting their positions within the airport traffic pattern, corroborating their reports that they did so. It could not be determined why neither pilot heard the other pilot's position reports; however, it is likely that they were not adequately monitoring other aircraft position reports while in the airport traffic pattern. If either pilot had heard the other pilot's position reports, it is likely that the collision would not have occurred.
Quoted verbatim from the NTSB record.
Aircraft involved
| Aircraft | Registration | Operator | Damage |
|---|---|---|---|
| Piper PA-22-135 | N1540P | Christopher Jordan | Substantial |
| Piper PA-28R-200 | N2108T | - | Substantial |
Other Piper PA-22 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 11 Dec 2013 | Piper PA-22-108 | Oscoda, Michigan, United States | - | No injuries | - |
| 16 Aug 2013 | Piper PA-22-150 | Indian Trail, North Carolina, United States | Darrell Hogue | No injuries | - |
| 12 May 2013 | Piper PA-22-160 | Pella, Iowa, United States | Daniel M. Adams | No injuries | - |
| 4 Oct 2013 | Piper PA-22-135 | Selinsgrove, Pennsylvania, United States | - | Serious injuries | - |
| 25 Aug 2013 | Piper PA-22-108 | Faribault, Minnesota, United States | George Gleim | No injuries | - |
| 16 Jul 2013 | Piper PA-22-125 | Mapleton, Minnesota, United States | McCarty Michael H | No injuries | - |
All 3,095 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 18 Apr 2013 | American Legend AL3 | Rexburg, Idaho, United States | Roy S. Webster | No injuries | - |
| 7 Sep 2013 | Scheel Stanley K KITFOX-SERIES 7 | Cascade, Idaho, United States | - | No injuries | - |
| 25 Jul 2013 | Piper PA-18 | Challis, Idaho, United States | Frank O Blomquist | No injuries | - |
| 25 Jul 2013 | Cessna A185F | Pocatello, Idaho, United States | Mathews Nicholas A | No injuries | - |
| 6 Nov 2013 | Cessna U206F | Donnelly, Idaho, United States | McCall Aviation Inc. | Fatal | 3 |
| 14 Jun 2013 | Cessna T210N | Salmon, Idaho, United States | Scott Patrick | No injuries | - |