# Accident 20000215041691A: Cessna 172N, Palm Springs, CA, February 15, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 15, 2000, 17:29 local time
- Place: Palm Springs, CA
- Airport: Palm Springs Regional Airport
- Damage: Substantial damage
- Collision: Midair collision, first aircraft
- Phase of flight: In Traffic Pattern-Circling
- Operating rules: General operating rules (Part 91)
- Location: 33.8333° N, 116.5167° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.8333&lon=-116.5167&mi=10
- Aircraft: N6479D, a cancelled registration (https://openairdocs.org/deregistered/N6479D-2012-08-23) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,420 total, 520 in this make and model, 180 in the last 90 days
- NTSB investigation: [NTSB LAX00FA101](https://openairdocs.org/ntsb/LAX00FA101) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000215041691A

## Narrative

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

(-23) ON FEBRUARY 15, 2000, AT 1729 HOURS PST, A CESSNA 172N, N6479D, COLLIDED IN MIDAIR WITH A PIPER PA-28-140, N84PB, WHILE IN THE TRAFFIC PATTERN AT PALM SPRINGS, CA. THE CESSNA WAS SUBSTANTIALLY DAMAGED AND THE CERTIFIED FLIGHT INSTRUCTOR AND HIS TWO STUDENTS RECEIVED MINOR INJURIES. THE PIPER SUSTAINED MINOR DAMAGE, HOWEVER, NEITHER OF THE CERTIFIED FLIGHT INSTRUCTORS NOR THEIR STUDENTS WERE INJURED. THE CESSNA AND THE PIPER WERE BOTH BEING OPERATED AS INSTRUCTIONAL FLIGHTS. THE REMAINING DATA ABOUT THE STUDENT PILOT WILL BE ADDED IN AN AMENDMENT.

## 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 LAX00FA101](https://openairdocs.org/ntsb/LAX00FA101), Feb 16, 2000: Cessna 172N (N6479D), Palm Springs, CA, substantial damage. Probable cause: the failure of both flight crews to see and avoid the other airplane while operating in the traffic pattern, which resulted in a mid-air collision. A contributing factor was the failure of the…

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.