Piper PA-34-200 N222ES
7 October 2000 · San Dimas, California, United States · Fatal
Summary
On 7 October 2000 at about 02:38 local time, a Piper PA-34-200 registered N222ES was involved in an accident near San Dimas, California, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 02:38
- Classification
- Accident
- Location
- San Dimas, California, United States
- Nearest airport
- Brackett Field (POC)
- Coordinates
- 34.1492, -117.7833
- Aircraft
- Piper PA-34-200
- Registration
- N222ES
- Category
- Airplane
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Instructional
- Phase of flight
- Not recorded
- Route
- Chino → Brackett Field
- Aircraft damage
- Destroyed
- Weather
- IMC
- Light
- Night
- NTSB number
- LAX01FA004
People
2 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 0 |
Probable cause
The pilots becoming lost and disoriented during an improperly conducted IFR approach, and subsequent missed approach, that led to a collision with rising mountainous terrain. Also causal was the local controller canceling the IFR approach when the pilot specifically stated he wanted to continue the IFR approach, and the local controller, as well as sector controllers failure to issue a unsafe proximity to terrain safety alert to the pilots (MSAW alert) as required by the Air Traffic Control Handbook.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The airplane collided with rising mountainous terrain while executing a missed approach procedure in instrument conditions during an instructional flight. At 1929 the TRACON controller (POMR) cleared the airplane for the VOR-A approach, and advised the pilot to contact the tower. The pilot acknowledged, then contacted the ATCT local controller (LC) and stated they were on the VOR-A approach outside of the final approach fix (FAF). Two minutes later the POMR controller, after observing the aircraft's target off course, contacted the LC to ask why the airplane was circling the airport. The LC stated he would find out and get back to the POMR controller. The LC asked the pilot if he wished to cancel IFR or continue the approach. The pilot replied that he wanted to continue and the LC told him to report the runway in sight. The LC, who was monitoring the flight's target track on the tower's DBRITE radar display, also informed the pilot that they appeared to be west of course. At 1932:20 the LC asked if they had the airport in sight. The pilot replied they had the airport in sight. The LC then contacted POMR and advised that the pilot was canceling IFR and had the airport in sight. The POMR controller then dropped the accident airplane's data block from his radar display. 47 seconds later, the LC asked the pilot to confirm he had the runway in sight. The pilot replied in the negative. The controller then asked if the pilot wanted the missed approach. The pilot replied that he had the ground and a freeway in sight. The pilot was instructed to continue and report the airport in sight. A few seconds later the pilot again reported the airport in sight, and was cleared to land runway 26L. At 1934:25 the LC asked the pilot what he was doing and if he had the airport in sight. The pilot asked if anything was wrong. The controller advised the pilot he was now three miles west of the airport and suggested he turn to a heading of 080-degrees. The controller also told the pilot to maintain visual flight conditions, and to report the runway in sight. At 1936:02 the controller advised the pilot the airport was 1.5 miles at the pilot's 12:00 o'clock position. He also asked if the pilot had the airport in sight. The pilot replied negatively. The controller instructed the pilot to make a 10-degree right turn to enter the downwind. The controller again informed the pilot that the airport was a little over a mile at their 12:00 position. The pilot replied he had the airport in sight. The controller instructed the pilot not to lose sight of the airport again, and cleared him to land. After observing the flight deviate from a track to the airport, at 1939:29 the controller asked the pilot for their current heading. The pilot then requested a missed approach. The controller instructed the pilot to execute the missed approach and to standby for a frequency change. The LC then called the TRACON sector controller and a discussion ensued between the two about the flight's VFR versus IFR status, with the TRACON controller saying that he thought the pilot had cancelled IFR and went VFR. The LC controller stated that "he had cancelled, he had the airport in sight, he lost sight of the airport, and he is asking me now if he can go missed approach so I don't know what to do with him." The Local Controller said he could work the pilot and try and get him back to the airport unless POMR wanted to take him. POMR stated that if the pilot was IMC and did not have the airport in sight that "I would have him turn southbound immediately." The LC then told the pilot to turn south and climb immediately to 5,000 feet. There was no response by the flight. Review of the recorded radar data disclosed that beginning at 1933:10 (about 5 minutes before the accident), the Minimum Safe Altitude Warning (MSAW) system was flashing an alert on both the TRACON controllers display and the DBRITE display in the tower; however, after the TRACON controller dropped the airplane's data tag the MSAW alert was automatically suppressed at the TRACON. Review of the recorded air/ground communications tapes disclosed that at no time did either controller issue an alert advisory for terrain avoidance to the flight.
Quoted verbatim from the NTSB record.
Other Piper PA-34 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 9 Apr 2000 | Piper PA-34-200T | Fayetteville, Arkansas, United States | - | No injuries | - |
| 27 Feb 2000 | Piper PA-34-200 | Big Bear City, California, United States | Kenneth K. Gheysar | Minor injuries | - |
| 1 Sep 2000 | Piper PA-34-200T | Meridianville, Alabama, United States | Harvey B. Wasserman | No injuries | - |
| 28 Jul 2000 | Piper PA-34-200T | Harbor Springs, Michigan, United States | Bear River Aviation | No injuries | - |
| 22 Oct 2000 | Piper PA-34 | Chacabuco, Argentina | Servicios Aereos Bahienses | Fatal | 11 |
| 28 Oct 2000 | Piper PA-34-200T | Fort Collins, Colorado, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 4 Aug 2000 | Piper PA-30 | Davis, California, United States | Travis AFB Aeroclub | No injuries | - |
| 9 Aug 2000 | Cessna 150H | Corona, California, United States | - | No injuries | - |
| 14 Feb 2000 | Cessna 182L | Coulterville, California, United States | - | Fatal | 2 |
| 31 May 2000 | Cessna 152 | Palm Springs, California, United States | The FLT School At Palm Springs | Fatal | 2 |
| 6 Nov 2000 | Cessna 340A | Selma, California, United States | Yecny Enterprises, Inc. | Fatal | 1 |
| 16 Feb 2000 | Cessna 172N | Palm Springs, California, United States | Bermuda Dunes Air Service | Minor injuries | - |