Mid-air collision Accident Cessna 182Q Skylane N759XA,
ASN logo
ASN Wikibase Occurrence # 45188
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 17 June 2003
Time:19:51
Type:Silhouette image of generic C182 model; specific model in this crash may look slightly different    
Cessna 182Q Skylane
Owner/operator:Flying Double Eagle Inc.,
Registration: N759XA
MSN: 18266330
Year of manufacture:1978
Fatalities:Fatalities: 2 / Occupants: 2
Other fatalities:3
Aircraft damage: Destroyed
Category:Accident
Location:Deerfield Beach, FL -   United States of America
Phase: En route
Nature:Private
Departure airport:Fort Lauderdale, FL (FLL)
Destination airport:Boca Raton, FL (BCT)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
N4903F, a Cessna 172N, and N759XA, a Cessna 182Q, collided while in cruise flight, during daylight visual meteorological conditions, in class E airspace, over the Atlantic ocean, about 300 yards east of the Deerfield Beach pier, Deerfield Beach, Florida. The airplane wreckages descended, impacted the ocean, and came to rest in about 38 feet of water. Both airplanes were destroyed, and all occupants received fatal injuries. The Cessna 172 had departed Fort Lauderdale Executive Airport about 1835, and had proceeded north. He had contacted PBI TRACON for authorization and radar advisory service, and was assigned a transponder code of 0205. At 1942:07, when preparing to exit PBI's airspace, the PBI controller instructed the pilot of Cessna 172 to remain on the same transponder code, and told him that radar service was terminated, and to contact Boca tower, "one one eight point four two for transition." The pilot of the Cessna 172 read back the frequency, and acknowledged. At this time radar indicated the Cessna 172 was about 10 miles south of PBI, and about 8 miles north-northeast of BCT. At 1943:30 radar indicated that the Cessna 172's transponder code changed from 0205 to 1200. At 1944:25, the pilot of Cessna 172 contacted Boca Raton tower (BCT) and said, "Skyhawk four niner zero three foxtrot, about seven miles north over the shoreline, would like to, to Lauderdale Executive, would like to transition your airspace please." The controller said, "zero three fox I believe that is, transition southbound approved, the altimeter two nine nine six, report east." The pilot of the Cessna 172 read back the altimeter setting. At 1942, the pilot of the Cessna 182 had left the Bahamas , and he had landed and cleared customs in Fort Lauderdale, and was at the time of the accident continuing on to his final destination, Boca Raton, Florida. At 1946:25, the pilot of Cessna 182 contacted Pompano Beach tower (PMP) and advised that he was "northbound, VFR along the beach landing Boca Raton." The PMP controller acknowledged and advised the pilot to "report passing east of the field." At 1948:46, the pilot of N47DM, an uninvolved airplane, called BCT tower, and requested to taxi to the active runway. The controller acknowledged and the pilot said he would like to pick up his IFR clearance. During this radio communications exchange, radar indicated the Cessna 172 passed east of BCT, and there was no record of the pilot of the Cessna 172 having reported his position, east. At 1949:05, the pilot of the Cessna 182 transmitted to the Pompano (PMP) tower controller, "reporting east of the field." Radar indicted the Cessna 182 was about 2 miles east of PMP about that time. The PMP tower controller responded and instructed the pilot to contact Boca Raton (BCT) tower, and the pilot acknowledged. At 1949:11, the BCT controller read the IFR clearance to the pilot of N47DM, an uninvolved pilot, and the pilot read back the clearance. While the pilot of N47DM was reading back the IFR clearance on the ground control frequency, the pilot of the Cessna 182 was transmitting on the local control frequency saying, "seven five niner x-ray alpha good evening." At 1949:34, on the ground control frequency, the BCT controller said, "that is correct", and less than three seconds later, on the local control frequency, he said, "roger, no reported traffic south, frequency change approved, good night." At this time, radar indicated the Cessna 172 was 3 miles south southeast of BCT at 1,000 feet, and the Cessna 182 was 2 miles northeast of PMP at 1,000 feet. The airplanes were about 5 miles apart on opposite courses. At 1949:44, the pilot of Cessna 182 repeated, "even five niner x-ray alpha good evening." The BCT controller responded, "Cessna calling say again", to which the pilot repeated the information, and the controller confirmed the call sign. The pilot acknowledged and said, "one thousand feet, VFR northbound along the beach, six an
Probable Cause: **This case was revised 6/10/2005 and 2/24/2016. Refer to the public docket for this accident for details.**
The failure of the pilot of N4903F, the Cessna 172, and the pilot of N759XA, the Cessna 182, to see and avoid each other while operating in Class E airspace, resulting in a midair collision. Contributing to the accident was the lack of traffic information being provided to the pilot of the Cessna 182 about known traffic in the vicinity, because the controller forgot about the Cessna 172' s reported path and altitude, and the Cessna 172 pilot's change of his transponder code, which precluded the possibility of an ATC collision alert before the accident.

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20030625X00951&key=1

Revision history:

Date/timeContributorUpdates
28-Oct-2008 00:45 ASN archive Added
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
08-Dec-2017 18:50 ASN Update Bot Updated [Operator, Total fatalities, Total occupants, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org