FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04FA043 · Piper PA-30

17 Jan 2004 · Clearwater, FL, United States

Piper PA-30 and Cessna 150H · Accident: midair collision on approach

Report a problem

Event

NTSB case
MIA04FA043
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
1 · 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 · Piper PA-30

Aircraft type
Piper PA-30
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
N8735Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Winter Haven Regional Airport - Gilbert Field (KGIF), Winter Haven, FLTo Clearwater Air Park (KCLW), Clearwater, FL
Aircraft age
Not recorded
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
Approach · VFR pattern downwind
First occurrenceThe 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
Midair collision
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 · Cessna 150H

Aircraft type
Cessna 150
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
N6622S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Clearwater Air Park (KCLW), Clearwater, FLTo Clearwater Air Park (KCLW)
Aircraft age
Not recorded
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
Approach · VFR pattern downwind
First occurrenceThe 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
Midair collision
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Visual lookout, not maintained
  • Pilot of other aircraft › Visual lookout, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A Piper PA-30, and a Cessna 150H, collided in flight while in the traffic pattern. The pilot of the Piper airplane reported that after canceling his IFR clearance the controller warned him, "...that there had been numerous traffic in the vicinity of CLW [Clearwater]. I acknowledged and I changed my radio to 123.0 and began to monitor for traffic. I crossed the center of the airport from east to west at 1,500 feet. Once on the west side of CLW, I made a left turn and started my descent to traffic pattern altitude, at which time I announced my intentions to enter a left crosswind for runway 16." The flight turned onto the downwind leg and he announced that on the radio. He also reported that "up to this point, no traffic had been observed." He continued on the downwind leg and slowed the airplane, and was looking for traffic. When the flight was approximately two thirds down the downwind leg, the passenger began to shout "look out, look out, look out." He looked to the right and saw an airplane coming at us, which was so close he did not have time to react before the collision. He lost control of the airplane momentarily and then saw a glimpse of the aircraft to his left. A witness who was located east of the crash site reported seeing a Cessna airplane fly over his location south-southeast bound, then bank to the right towards a north-northwesterly direction. He observed the Piper airplane flying briefly in a southeasterly direction, then bank to the left towards a north-northwesterly direction. An individual on the ground at the destination airport, reported hearing the pilot of the Piper airplane make repetitive radio calls on the Common Traffic Advisory Frequency (CTAF) while in the traffic pattern, announcing the intention of landing on runway 16. The same individual who personally knows the pilot of the Cessna airplane, reported hearing him report crossing midfield at KCLW; the Cessna pilot did not report altitude or intention. The individual did not hear any other radio calls from the Cessna pilot. After the collision, the radar plot indicated the Piper airplane flew downwind, base, then onto final approach to runway 16. The Cessna crash site was located in close proximity to the last radar target. The pilot of the Piper airplane was last in contact with air traffic control and there was no reported communication difficulties. There was no record of communications from the pilot of the Cessna airplane with any FAA Air Traffic Control Facility. The pilot of the Piper airplane was heard to report on the UNICOM frequency his intention to land on runway 16, and also repetitive radio calls announcing his traffic pattern legs. The pilot of the Cessna airplane was heard to announce on the UNICOM that he was crossing midfield, but he did not announce his intention or altitude. Examination of the Piper airplane revealed paint transfer and damage to the right wing, vertical stabilizer, and upper surface of the left horizontal stabilator. Paint transfer was noted on the bottom fuselage skin of the Cessna near the landing gear attach point area. The No. 1 communication transceiver of the Piper was found set to 123.00 mHz, which is the CTAF for KCLW. The radio was operationally tested in the airplane postaccident and found to operate satisfactory. The only communication transceiver in the Cessna airplane was found set to 123.00 mHz, and during postaccident testing was noted to momentarily operate; impact damage precluded continued testing. VMC prevailed at the time of the accident. There were no preimpact failure or malfunction of the flight controls of both airplanes, and examination of the Cessna airplane's engine revealed no abnormalities. The AIM indicates to enter the traffic pattern at a 45 degree angle to the runway on the downwind leg.

Probable cause

The failure of both pilots to maintain adequate visual lookout while entering the traffic pattern (downwind leg) at an uncontrolled airport resulting in a midair collision.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04FA043
Event ID
20040203X00156
Case number
MIA04FA043
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 04a123e1cbdb36a480346924f30e1c78476da995c7c123149420f305119435b1; retrieved 2026-09-20T18:37:14.312Z.