Pattern Conflict at Clearwater Air Park
Two aircraft, one non-towered pattern, and the see-and-avoid principle under pressure — a midair collision scenario
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, on a local VFR flight. Elevation 71 ft MSL. It is a clear, calm Saturday morning: OAT 22°C, winds calm to 3 knots, visibility 10+ SM. The kind of day that brings every general-aviation pilot in the Tampa Bay area to the pattern.
KCLW is non-towered (CTAF 122.8). There is no ATC, no sequencing, no conflict alerts. Pilots self-announce on the CTAF: 'Clearwater traffic, Cessna [N-number] turning base Runway 16' — and rely entirely on see-and-avoid. The field is busy this morning: at least three other aircraft in the pattern, including a Piper Cherokee and a Cessna 172, both on downwind or base.
You are a Commercial pilot with roughly 400 hours total, 80 hours in the C182 Skylane. The C182 is a high-performance single: 230 hp Continental O-470, constant-speed prop, cowl flaps, fixed gear. It is faster, heavier, and more nose-heavy than the 172 you trained in. The workload is higher — prop RPM management, cowl flap cooling, and the energy of the airplane demands a disciplined, stabilized approach.
You are on a local flight: a 30-minute pattern work session to build C182 proficiency. You have completed two touch-and-goes on Runway 16 and are climbing back to pattern altitude (1,000 ft AGL) for a third approach. You are on the downwind leg, heading roughly 335° (reciprocal of Runway 16's 155° heading), at 1,200 ft AGL, at 90 KIAS, with flaps retracted. The prop is set to 2,000 RPM for descent, the cowl flaps are cracked open for cooling, and you are scanning ahead for traffic.
You hear a radio call: 'Clearwater traffic, Piper Cherokee, turning base Runway 16.' You do not see the Cherokee. You are on downwind; the Cherokee is on base — they should be below you and to your left. You should see them. You don't. You continue the descent and the turn toward base.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'C182'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about midair collision risk in a non-towered pattern? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB LAX06FA106B (2006, FATAL): A Cessna 172RG on an IFR departure and a Cessna 182Q on a VFR local flight collided in midair near Gillespie Field, San Diego, destroying both aircraft and killing three occupants. The probable cause was the failure of both pilots to maintain an adequate visual lookout due to their relative flight paths, which limited available visual cues. Contributing factors included ATC failure to issue a conflict alert and the task load of a CFI in the C172RG.
NTSB MIA03FA124B (2003, FATAL): A Cessna 172N and a Cessna 182Q collided in cruise flight over the Atlantic Ocean near Deerfield Beach, Florida, while operating in Class E airspace. The probable cause was the failure of both pilots to see and avoid each other. Contributing factors included lack of traffic information provided to the C182 pilot and the C172 pilot's change of transponder code.
NTSB LAX03FA066A (2003, FATAL): A Cessna 182H and a Grumman F6F-5 collided in midair approximately 1 mile east of Parker, Arizona during an air show. The probable cause was the failure of both pilots to see and avoid one another while maneuvering in the traffic pattern. A contributing factor was the inability of the Cessna pilot to communicate on the CTAF frequency due to radio limitations.
NTSB LAX02FA110B (2002, FATAL): A U.S. Army Pilatus UV-20A and a Cessna 182C collided in midair during skydiving operations over Marana, Arizona. The probable cause was the failure of both pilots to maintain an adequate visual lookout. A contributing factor was the Pilatus pilot's failure to report his proper position.
The common thread across all these accidents: in non-towered or low-radar-coverage environments, see-and-avoid is the ONLY collision avoidance tool. A radio call on CTAF tells other pilots where you *say* you are, but it does not guarantee they see you, understand your position, or maintain separation. The accidents happened at Gillespie Field (San Diego), Deerfield Beach (Florida), Parker (Arizona), and Marana (Arizona) — NOT at Clearwater Air Park. But the environment at KCLW is identical: non-towered, busy pattern, multiple aircraft, no ATC separation. The risk is real and local.
The scenario at KCLW is particularly unforgiving because the field is in the Tampa Bay area, which is busy with general aviation traffic. On a clear Saturday morning, the pattern can have 4–6 aircraft simultaneously. The off-field environment off both runway ends (Runway 16 and Runway 34) is dense development — there is no alternate landing surface if you need to go around or divert. You are committed to the pattern once you are in it.
The key lesson from all these accidents: aggressive visual scanning is not optional. On downwind, before you turn base, execute a deliberate scan of the base leg and final approach area — look left wing down, look ahead, look under the wing. If you do not have visual contact with another aircraft that just called on CTAF, extend downwind, climb out, or go around. A radio call is not a guarantee of separation. See-and-avoid is active, deliberate, and continuous.
Key lesson — In a non-towered pattern like KCLW, see-and-avoid is the only collision avoidance tool. A radio call on CTAF tells other pilots where you are, but it does not guarantee they see you. Aggressive visual scanning on downwind — before you turn base — is mandatory. If you do not have visual contact with another aircraft that called on CTAF, extend downwind, climb out, or go around. A go-around is not a failure; it is airmanship. The C182's higher speed and energy demand a stabilized, predictable approach — aggressive descents to land ahead of other traffic destabilize the approach and increase collision risk. Land behind other traffic. The pattern will still be there in 60 seconds.
Debrief — teaching points
See-and-avoid is active, not passive.
In a non-towered pattern, see-and-avoid is the ONLY collision avoidance tool. It is not passive — you do not just look out the window and hope you see traffic. It is active: you execute deliberate, aggressive visual scans at specific points in the pattern. On downwind, before you turn base, scan the base leg and final approach area hard. Look left wing down to clear your blind spot. Look ahead and below. If you do not have visual contact with another aircraft that just called on CTAF, do not assume they are where they said they are. Extend downwind, climb out, or go around. A radio call is not a guarantee of separation.
A radio call on CTAF does not guarantee separation.
When another pilot calls 'turning base Runway 16,' they are telling you where they *say* they are. But they may be higher or lower than you expect, closer or farther from the runway, or on a slightly different heading. The radio call is useful information, but it is not a guarantee of separation. You must visually confirm their position before you turn base yourself. If you cannot see them, extend downwind, climb out, or go around. The NTSB LAX06FA106B case involved both pilots making radio calls — and they still collided because neither pilot saw the other until it was too late.
The high-wing Cessna has a significant blind spot directly ahead and above.
The high wing of the C182 (and all Cessnas) creates a blind spot directly ahead and above the nose. Another aircraft can be in that zone and invisible to you. To clear this blind spot, you must deliberately bank the airplane slightly left or right to see under the wing. This is not optional — it is a required scan technique in a busy pattern. On downwind, before you turn base, bank left and look under the wing at the base leg and final approach area. This is how you see traffic that is ahead and below you.
Closure rate in a pattern can exceed 100 knots.
Two aircraft on converging headings in a pattern can close at a combined closure rate of 100+ knots. At that closure rate, the time from first visual contact to collision is measured in seconds — often less than 5 seconds. This is why aggressive visual scanning is mandatory. You must see the other aircraft early enough to have time to react. If you do not see them until they are 500 ft away, you may not have time to climb, turn, or descend to avoid them. The NTSB cases show that pilots often do not see the other aircraft until it is too late.
High workload reduces scanning effectiveness.
The C182 is a high-performance airplane: constant-speed prop, cowl flaps, higher speed, more energy. The workload on approach is higher than in a 172. Prop RPM management, cowl flap cooling, descent planning, and radio communication all compete for your attention. The busier you are, the less you scan for traffic. This is a documented human factors issue in the NTSB LAX06FA106B case — the CFI in the C172RG was task-loaded and did not see the C182Q. Manage your workload: set the prop and cowl flaps before you enter the pattern, plan your descent before you turn downwind, and keep radio calls brief. This frees up mental capacity for visual scanning.
A stabilized, predictable approach makes you easier to see and predict.
A stabilized approach — constant descent rate, constant airspeed (70 KIAS for the C182), on a known path — is easier for other pilots to see and predict. An aggressive descent, a steep turn, or a sudden altitude change makes you harder to see and harder to predict. In a busy pattern, fly a stabilized, predictable approach. Land behind other traffic if necessary. A go-around is always an option. The C182's higher speed and energy demand discipline — a fast or unstable approach floats and the nose drops into a porpoise. Stabilize the approach at 70 KIAS, descend at a constant rate, and land smoothly.
Built from the real accident record
Scenario built from NTSB LAX06FA106B (2006 C182Q / C172RG midair collision, Gillespie Field), MIA03FA124B (2003 C182Q / C172N midair collision, Deerfield Beach), LAX03FA066A (2003 C182H / F6F-5 collision, Parker AZ), and LAX02FA110B (2002 C182C / UV-20A collision, Marana AZ). Localized to KCLW non-towered pattern environment.
NTSB reports: LAX06FA106B · MIA03FA124B · LAX03FA066A · LAX02FA110B · WPR24LA167 · GAA19CA534 · WPR12LA023
ACS tasks: PA.I.F — Weather Information · PA.V.A — Preflight Inspection · PA.VIII.A — Approaches and Landings · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.113 · §91.155
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Cessna 182 Skylane scenarios · More scenarios at KCLW