ASN Wikibase Occurrence # 215958
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: | Saturday 29 September 2018 |
| Time: | 12:40 |
| Type: |  Diamond DA20-C1 |
| Owner/operator: | Aamro Aviation Corporation |
| Registration: | N397JA |
| MSN: | C0212 |
| Year of manufacture: | 2003 |
| Total airframe hrs: | 2776 hours |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Sebring, Highlands County, FL -
 United States of America
|
| Phase: | Landing |
| Nature: | Training |
| Departure airport: | Sebring, FL (SEF) |
| Sebring, FL (SEF) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The private pilot of the Piper airplane with a passenger on board was landing while the student pilot of the Diamond airplane with a flight instructor on board was performing touch-and-go landings on an intersecting runway in day visual meteorological conditions. Both airplanes were flying in left traffic patterns for their respective runways at the uncontrolled airport. The pilot of the Piper and the student pilot of the Diamond stated that they announced every leg of the traffic pattern on the airport’s published common traffic advisory frequency (CTAF). The Diamond landed, and just when the student was adding power to initiate a takeoff, the left wing of the Piper, which was landing and flaring just a few feet above the runway, impacted the tail of the Diamond. The flight instructor in the Diamond said he was looking for the Piper after he saw it flying in the vicinity of the airport but that he never saw it in the airport traffic pattern, while the pilot of the Piper did not report seeing the Diamond until just before the collision. Recordings of the airport's CTAF showed that radio calls from the Diamond were heard for every leg of the airport traffic pattern on the published CTAF frequency before the collision, but only two garbled radio calls from the Piper were heard on the published CTAF frequency. Postaccident examination of the Piper's transceiver revealed that it was set to a different frequency. The Piper's transceiver was then set to the correct CTAF frequency, and the communication was clear. Therefore, it is likely that the pilot of the Piper failed to use the correct CTAF frequency when he announced his airplane's position in the airport traffic pattern.
Probable Cause: The inability of the pilot of the Piper and the student pilot and flight instructor of the Diamond to see and avoid the other airplane. Contributing to the collision was the Piper pilot’s failure to use the correct common traffic advisory frequency to announce his airplane's position.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N397JA
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 02-Oct-2018 18:02 | Captain Adam | Added |
| 04-Oct-2018 05:55 | Anon. | Updated [Total occupants] |
| 27-Nov-2019 07:16 | ASN Update Bot | Updated [Time, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation