ERA18LA268 · Diamond DA20 C1
Aamro Aviation Diamond DA20 C1 and Piper PA28R 180 · Accident: collision during takeoff/landing
Event
- NTSB case
- ERA18LA268
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Diamond DA20 C1
- Aircraft type
- Diamond DA20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N397JA
- Operator
- Aamro Aviation
- Onboard fatalities
- Unknown
- Route
- From Sebring Regional Airport (SEF), Sebring, FLTo Sebring Regional Airport (SEF), Sebring, FL
- Aircraft age
- About 15 years (built 2003)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Piper PA28R 180
- Aircraft type
- Piper PA28
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3907T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Peter O Knight Airport (TPF), Tampa, FLTo Sebring Regional Airport (SEF), Sebring, FL
- Aircraft age
- About 51 years (built 1967)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision during takeoff/landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18LA268
- Event ID
- 20180929X13051
- Case number
- ERA18LA268
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: be0123b5660b9a7bb43a83d88854fd9e6e2c8d2a8f020fcb8a4461d5582dae38; retrieved 2026-09-13T18:30:56.643Z.