# NTSB LAX00FA101: Cessna 172N, N6479D, Palm Springs, CA, February 16, 2000 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Field investigation · Final report - Date: February 15, 2000, 17:29 local (Feb 16, 2000, 01:29 UTC) - Place: Palm Springs, CA - Coordinates: 33.833332, -116.51667 - Nearby events: https://openairdocs.org/map.md?lat=33.8333&lon=-116.5167&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 3 minor, 2 uninjured - Status: Completed, report November 25, 2003 - Report: Approved by Office Director - Parties: National Air Traffic Controllers Association, Federal Aviation Administration, FAA Office of Accident Investigation - NTSB case key (mKey): 48669 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX00FA101 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/48669/pdf - Page: https://openairdocs.org/ntsb/LAX00FA101 ## Probable cause (aircraft 2) 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 arriving aircraft to comply with air traffic control requests by not issuing a position report. ## Probable cause (aircraft 1) 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 arriving aircraft to comply with air traffic control requests by not issuing a position report. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Midair collision, approach - vfr pattern - downwind - visual separation - not maintained, flightcrew (cause) - visual separation - not maintained, flightcrew of other aircraft (cause) - instructions,written/verbal - not complied with, flightcrew of other aircraft (contributing factor) - Forced landing, descent - emergency - On ground/water encounter with terrain/water, landing - flare/touchdown - Midair collision, approach - vfr pattern - downwind - visual separation - not maintained, flightcrew - visual separation - not maintained, flightcrew of other aircraft - instructions,written/verbal - not complied with, flightcrew ## Analysis (aircraft 2) A high-wing airplane and low-wing airplane collided in mid-air while operating in the traffic pattern at a controlled airport. The air traffic controller issued traffic advisories to both aircraft, and each pilot acknowledged the advisories. The controller also requested that the low-wing airplane, which was inbound to the airport, to "report two miles out on the forty five." The pilot of the low-wing airplane acknowledged the request; however, there was no evidence that the pilot gave the report. The high-wing airplane was in the process of making a right turn from crosswind to the downwind leg when the low-wing airplane (inbound on a 30-degree entry to downwind) impacted the high-wing airplane's left wing with its propeller and lower engine cowling. The high-wing airplane subsequently lost control, the flight instructor recovered, and conducted an emergency landing in a desert area adjacent to the airport. The low-wing airplane continued to the airport and landed without further incident. Review of the air traffic control system revealed that the control tower was not utilizing the Digital Bright Radar Indicator Tower Equipment (D-BRITE), which would provide controllers with additional radar data on the airplanes, because it was out of service due to being unreliable. However, FAA directives state that the D-BRITE system was never intended to be utilized for traffic separation. The pilots were informed that they did not have radar coverage while in the controlled airspace via the Automatic Terminal Information Service. Additionally, the Airman's Information Manual states that regardless of radar coverage, pilots have the sole responsibility to see and avoid other aircraft. ## Analysis (aircraft 1) A high-wing airplane and low-wing airplane collided in mid-air while operating in the traffic pattern at a controlled airport. The air traffic controller issued traffic advisories to both aircraft, and each pilot acknowledged the advisories. The controller also requested that the low-wing airplane, which was inbound to the airport, to "report two miles out on the forty five." The pilot of the low-wing airplane acknowledged the request; however, there was no evidence that the pilot gave the report. The high-wing airplane was in the process of making a right turn from crosswind to the downwind leg when the low-wing airplane (inbound on a 30 degree entry to downwind) impacted the high-wing airplane's left wing with its propeller and lower engine cowling. The high-wing airplane subsequently lost control, the flight instructor recovered, and conducted an emergency landing in a desert area adjacent to the airport. The low-wing airplane continued to the airport and landed without further incident. Review of the air traffic control system revealed that the control tower was not utilizing the Digital Bright Radar Indicator Tower Equipment (D-BRITE), which would provide controllers with additional radar data on the airplanes, because it was out of service due to being unreliable. However, FAA directives state that the D-BRITE system was never intended to be utilized for traffic separation. The pilots were informed that they did not have radar coverage while in the controlled airspace via the Automatic Terminal Information Service. Additionally, the Airman's Information Manual states that regardless of radar coverage, pilots have the sole responsibility to see and avoid other aircraft. ## Factual narrative (aircraft 2) HISTORY OF FLIGHT On February 15, 2000, at 1729 Pacific standard time, a Cessna 172N high-wing airplane, N6479D, collided in midair with a Piper PA-28-140 low-wing airplane, N84PB, while in the traffic pattern at the Palm Springs International Airport (PSP), Palm Springs, California. The Cessna was substantially damaged and the certified flight instructor and two students received minor injuries. The Piper sustained minor damage; however, neither the certified flight instructor nor the student were injured. The Cessna and the Piper were registered to private individuals and were being operated as instructional flights under 14 Code of Federal Regulations Part 91. The Cessna was operated by Bermuda Dunes Air Service of Bermuda Dunes, California, and the Piper was operated by Alliance International Aviation, Chino, California. The Cessna was originating from PSP at the time of the accident, while the Piper flight had originated from the Chino Airport, Chino, California, about 1650, and was destined for PSP. Visual meteorological conditions prevailed at the time and no flight plans were filed. Review of air traffic control radar data and communications by the National Transportation Safety Board revealed the following information: At 1719:01, N84PB initiated contact with PSP Air Traffic Control Tower (ATCT) Approach Control. The approach controller radar identified N84PB 14 nautical miles west-northwest of PSP. The pilot advised the controller that he had Automatic Terminal Information Service (ATIS) information golf and intended on landing at PSP. The approach controller issued N84PB a transponder code of 0402, and instructed N84PB to "follow the 10 freeway at or above 2,500 feet for right traffic runway 31L." The pilot acknowledged the instructions. At 1723:40, the approach controller instructed N84PB to contact PSP tower on frequency 119.7, to which the pilot acknowledged. When the approach controller handed off N84PB to the control tower, the airplane was located approximately 7 nautical miles northwest of the airport. Meanwhile, prior to N84PD's switch to the control tower frequency, N6479D called ground control and requested "taxi for touch and goes" at 1720:27. Ground control instructed N6479D to taxi to runway 31R. At 1723, N6479D called the PSP local controller and advised that they were "holding short of 31R for touch and goes." At 1724:22, N84PB called the local controller and reported "over the 10 freeway at 3,000 for landing with information golf." At that point, N84PB was approximately 5.5 nautical miles from the center of the airport. The local controller acknowledged and instructed N84PB to "make right traffic runway three one right report two miles out on the forty five." The pilot of N84PB replied "three one right report two miles out, papa bravo." After clearing other traffic, the local controller cleared N6479D at 1725:21, to "follow the Cessna upwind right closed traffic approved, runway three one right, cleared for takeoff." At 1725:39, the local controller advised N84PD that "two Cessnas in the right closed traffic pattern." The pilot replied "papa bravo, looking." At this time, N84PB was 3.5 nautical miles from the center of the airport, or 3.1 miles from the departure end of runway 31R. This position equated with approximately 2.5 nautical miles from a point abeam the departure end of runway 31R on a downwind leg. Radar data indicated that N84PB's ground track was turning to the right, and was passing through 2,400 feet with a descent rate of approximately 600 feet per minute. At 1726:07, the local controller advised N6479D that "traffic's inbound from the northwest for right traffic, a Cherokee." The pilot of N6479D acknowledged. At this point, radar data depicted N6479D established on the upwind leg, approximately over the departure end of 31R. N84PB was approximately 2.5 nautical miles northeast of the departure end of 31R with a ground track of approximately 165 degrees magnetic. At 1726:30, N84PB passed approximately 2 nautical miles north of the departure end of runway 31R. At 1726:48, N84PB passed approximately 2 nautical miles north of the airport center point. No other transmissions or interference were heard on the recorded tower voice communications between 1726:48 and 1727:19. Radar data indicated that the aircraft targets merged approximately 1 nautical mile northeast of the airport at 1,300 feet msl. The Cessna was in a right banked turn to the downwind. The Piper was entering the downwind on about a 30-degree intercept angle. At 1727:20, the pilot of N6479D transmitted a mayday call indicating that they had collided with another airplane and the pilot was having trouble controlling the airplane. The airplane entered an uncommanded descending left spiral. The flight instructor took over control of the airplane, recovered, and performed a forced landing to desert terrain. The local controller observed the airplane perform a forced landing in an open desert area northeast of the airport. After the impact, N84PB requested a low pass to have the local controller observe the landing gear condition. The local controller cleared N84PB for a fly-by at tower level and reported that the landing gear appeared to "be correct." The local controller then cleared N84PB for landing on 31R and at 1733:29, N84PB landed without further incident. During post-accident interviews with both flight instructors, each acknowledged receiving a traffic advisory; however, neither instructor reported seeing the other aircraft at any time prior to the collision. PERSONNEL INFORMATION The flight instructor for the Cessna airplane held instructor ratings in single engine, multiengine, and instrument airplanes. He also held a commercial pilot certificate with ratings for single engine, multiengine, and instrument airplanes. The flight instructor was issued a first-class medical certificate with no limitations on January 11, 2000. According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the flight instructor accumulated a total of 1,431 flight hours, of which 423 hours were accumulated in the same make and model as the accident airplane. He also reported having accumulated a total of 423 hours of instructor flight hours, of which 335 hours were instructed in the same make and model as the accident airplane. The student, who was flying the Cessna airplane at the time of the accident, had accumulated 25 hours of total flight time, of which all 25 hours were accumulated in the accident airplane make and model. The rear seat passenger in the Cessna airplane also held a student pilot certificate and had relinquished the controls to the flying student prior to the last takeoff. The flight instructor for the Piper airplane held instructor ratings in single engine, multiengine, and instrument airplanes. He also held a commercial pilot certificate with ratings for single engine, multiengine, and instrument airplanes. He was issued a second-class medical certificate on May 24, 1999, with a limitation to wear glasses. According to the Pilot/Operator Aircraft Accident Report, the flight instructor accumulated a total of 4,250 flight hours, of which 150 hours were accumulated in the same make and model as the accident airplane. He also reported having accumulated a total of 2,810 hours as a flight instructor, of which 120 hours were instructed in the same make and model as the accident airplane. The student, who was flying the Piper airplane at the time of the accident, had accumulated 22 total flight hours, of which approximately 3 hours were flown in the accident airplane make and model. WRECKAGE AND IMPACT INFORMATION According to witnesses, during the collision, the left wingtip from the high-wing Cessna was struck by the propeller and lower engine cowling of the overtaking low-wing Piper. The Cessna's left wing from ## Factual narrative (aircraft 1) HISTORY OF FLIGHT On February 15, 2000, at 1729 Pacific standard time, a Cessna 172N high-wing airplane, N6479D, collided in midair with a Piper PA-28-140 low-wing airplane, N84PB, while in the traffic pattern at the Palm Springs International Airport (PSP), Palm Springs, California. The Cessna was substantially damaged and the certified flight instructor and two students received minor injuries. The Piper sustained minor damage; however, neither the certified flight instructor nor the student were injured. The Cessna and the Piper were registered to private individuals and were being operated as instructional flights under 14 Code of Federal Regulations Part 91. The Cessna was operated by Bermuda Dunes Air Service of Bermuda Dunes, California, and the Piper was operated by Alliance International Aviation, Chino, California. The Cessna was originating from PSP at the time of the accident, while the Piper flight had originated from the Chino Airport, Chino, California, about 1650, and was destined for PSP. Visual meteorological conditions prevailed at the time and no flight plans were filed. Review of air traffic control radar data and communications by the National Transportation Safety Board revealed the following information: At 1719:01, N84PB initiated contact with PSP Air Traffic Control Tower (ATCT) Approach Control. The approach controller radar identified N84PB 14 nautical miles west-northwest of PSP. The pilot advised the controller that he had Automatic Terminal Information Service (ATIS) information golf and intended on landing at PSP. The approach controller issued N84PB a transponder code of 0402, and instructed N84PB to "follow the 10 freeway at or above 2,500 feet for right traffic runway 31L." The pilot acknowledged the instructions. At 1723:40, the approach controller instructed N84PB to contact PSP tower on frequency 119.7, to which the pilot acknowledged. When the approach controller handed off N84PB to the control tower, the airplane was located approximately 7 nautical miles northwest of the airport. Meanwhile, prior to N84PD's switch to the control tower frequency, N6479D called ground control and requested "taxi for touch and goes" at 1720:27. Ground control instructed N6479D to taxi to runway 31R. At 1723, N6479D called the PSP local controller and advised that they were "holding short of 31R for touch and goes." At 1724:22, N84PB called the local controller and reported "over the 10 freeway at 3,000 for landing with information golf." At that point, N84PB was approximately 5.5 nautical miles from the center of the airport. The local controller acknowledged and instructed N84PB to "make right traffic runway three one right report two miles out on the forty five." The pilot of N84PB replied "three one right report two miles out, papa bravo." After clearing other traffic, the local controller cleared N6479D at 1725:21, to "follow the Cessna upwind right closed traffic approved, runway three one right, cleared for takeoff." At 1725:39, the local controller advised N84PD that "two Cessnas in the right closed traffic pattern." The pilot replied "papa bravo, looking." At this time, N84PB was 3.5 nautical miles from the center of the airport, or 3.1 miles from the departure end of runway 31R. This position equated with approximately 2.5 nautical miles from a point abeam the departure end of runway 31R on a downwind leg. Radar data indicated that N84PB's ground track was turning to the right, and was passing through 2,400 feet with a descent rate of approximately 600 feet per minute. At 1726:07, the local controller advised N6479D that "traffic's inbound from the northwest for right traffic, a Cherokee." The pilot of N6479D acknowledged. At this point, radar data depicted N6479D established on the upwind leg, approximately over the departure end of 31R. N84PB was approximately 2.5 nautical miles northeast of the departure end of 31R with a ground track of approximately 165 degrees magnetic. At 1726:30, N84PB passed approximately 2 nautical miles north of the departure end of runway 31R. At 1726:48, N84PB passed approximately 2 nautical miles north of the airport center point. No other transmissions or interference were heard on the recorded tower voice communications between 1726:48 and 1727:19. Radar data indicated that the aircraft targets merged approximately 1 nautical mile northeast of the airport at 1,300 feet msl. The Cessna was in a right banked turn to the downwind. The Piper was entering the downwind on about a 30-degree intercept angle. At 1727:20, the pilot of N6479D transmitted a mayday call indicating that they had collided with another airplane and the pilot was having trouble controlling the airplane. The airplane entered an uncommanded descending left spiral. The flight instructor took over control of the airplane, recovered, and performed a forced landing to desert terrain. The local controller observed the airplane perform a forced landing in an open desert area northeast of the airport. After the impact, N84PB requested a low pass to have the local controller observe the landing gear condition. The local controller cleared N84PB for a fly-by at tower level and reported that the landing gear appeared to "be correct." The local controller then cleared N84PB for landing on 31R and at 1733:29, N84PB landed without further incident. During post-accident interviews with both flight instructors, each acknowledged receiving a traffic advisory; however, neither instructor reported seeing the other aircraft at any time prior to the collision. PERSONNEL INFORMATION The flight instructor for the Cessna airplane held instructor ratings in single engine, multiengine, and instrument airplanes. He also held a commercial pilot certificate with ratings for single engine, multiengine, and instrument airplanes. The flight instructor was issued a first-class medical certificate with no limitations on January 11, 2000. According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the flight instructor accumulated a total of 1,431 flight hours, of which 423 hours were accumulated in the same make and model as the accident airplane. He also reported having accumulated a total of 423 hours of instructor flight hours, of which 335 hours were instructed in the same make and model as the accident airplane. The student, who was flying the Cessna airplane at the time of the accident, had accumulated 25 hours of total flight time, of which all 25 hours were accumulated in the accident airplane make and model. The rear seat passenger in the Cessna airplane also held a student pilot certificate and had relinquished the controls to the flying student prior to the last takeoff. The flight instructor for the Piper airplane held instructor ratings in single engine, multiengine, and instrument airplanes. He also held a commercial pilot certificate with ratings for single engine, multiengine, and instrument airplanes. He was issued a second-class medical certificate on May 24, 1999, with a limitation to wear glasses. According to the Pilot/Operator Aircraft Accident Report, the flight instructor accumulated a total of 4,250 flight hours, of which 150 hours were accumulated in the same make and model as the accident airplane. He also reported having accumulated a total of 2,810 hours as a flight instructor, of which 120 hours were instructed in the same make and model as the accident airplane. The student, who was flying the Piper airplane at the time of the accident, had accumulated 22 total flight hours, of which approximately 3 hours were flown in the accident airplane make and model. WRECKAGE AND IMPACT INFORMATION According to witnesses, during the collision, the left wingtip from the high-wing Cessna was struck by the propeller and lower engine cowling of the overtaking low-wing Piper. The Cessna's left wing from ## Aircraft 1 - Registration: [N6479D](https://openairdocs.org/deregistered/N6479D-2012-08-23), registration cancelled 2012-08-23, S/N 17272827, built 1979 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17272827 - Airframe hours: 9054 - Engines: Lycoming O-360-A4M 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Bermuda Dunes Air Service, doing business as Bermuda Dunes Air Service - Registered owner: Pending - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 13, 2000, 10 hours before - Departed: PSP, Palm Springs, CA - Destination: UDD, Bermuda Dunes, CA - Airport: PSP, Palm Springs International ## Aircraft 2 - Registration: N84PB (not matched to a registry record) - Reported make and model: Piper PA-28-140 - Category: Airplane - Serial number: 28-24584 - Airframe hours: 7404 - Engines: Lycoming O-320-E2A 140 horsepower reciprocating - Damage: Minor damage - Flight: Instructional, Part 91 - Operator: Alliance International Aviation, doing business as Alliance International Aviation - Registered owner: Patrick A. Brass - Airworthiness certificate: Standard, Normal - Last inspection: Annual, May 12, 1999, 130 hours before - Departed: CNO, Chino, CA - Destination: PSP - Airport: PSP, Palm Springs International, runway 31R, 4,952 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor, aircraft N6479D; age 28; injuries: minor; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; last flight review July 29, 1999; seat: right; flight hours: 1,431 total, 423 in this make and model, 1,367 as pilot in command, 246 in the last 90 days, 94 in the last 30 days, 5 in the last 24 hours - Student pilot, aircraft N6479D; age 28; injuries: minor; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 25 total, 25 in this make and model, 10 as pilot in command, 10 in the last 90 days, 5 in the last 30 days, 1 in the last 24 hours - Flight instructor, aircraft N84PB; age 54; injuries: none; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; last flight review May 27, 1999; flight hours: 4,250 total, 150 in this make and model, 4,140 as pilot in command, 120 in the last 90 days, 35 in the last 30 days, 4 in the last 24 hours - Student pilot, aircraft N84PB; age 32; injuries: none; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 22 total, 3 in this make and model, 3 as pilot in command, 22 in the last 90 days, 16 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 200° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 39 °F - Altimeter: 30.00 inHg - Observed at: PSP, 1 nm away ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20000215041691A](https://openairdocs.org/incident/20000215041691A), Feb 15, 2000: Cessna 172N, Palm Springs, CA, Substantial damage. (-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… - [Accident 20000215009799A](https://openairdocs.org/incident/20000215009799A), Feb 15, 2000: Piper PA28140, Palm Springs, CA, No damage. (-23) On feb. 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… 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. --- 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.