Pattern Conflict at Lakeland
High workload, multiple aircraft in the pattern, and a controller's incomplete clearance — a midair collision risk in busy VFR traffic
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, a busy Saturday afternoon in early spring. Field elevation 142 ft MSL. You are a Private pilot with roughly 250 hours total, current and proficient. This is your third visit to KLAL; you know the field layout but not intimately.
Current conditions: VFR, visibility 10 SM, scattered clouds at 3,500 ft, wind 120° at 12 gusting to 18 knots. Runway 10 is the active runway (heading 090°). The crosswind component is roughly 8–10 knots steady, gusting to 12 knots — within your demonstrated crosswind capability (Cessna 172M is 12 knots demonstrated), but the gusts are noticeable.
You have completed your approach briefing. You are on a 5-mile final for Runway 10, descending through 800 ft AGL, airspeed 70 KIAS (slightly above Vref of 63 KIAS to maintain control in the gusts), flaps 20°. The tower cleared you to land on Runway 10 five minutes ago. You have been monitoring tower frequency; there is other traffic in the pattern — you heard at least two other aircraft check in on downwind and base in the last few minutes.
Aircraft: Cessna 172M, solo, 2,100 lb gross weight, within limits. Carbureted Lycoming O-320, 150 hp, fixed-pitch prop, fixed gear. Vacuum-driven steam panel (attitude indicator, heading indicator). Radio is working; you are in two-way communication with KLAL tower.
Pilot: You. You are current and proficient, but you have not flown into KLAL in six months. The pattern is busier than you expected. You are focused on the approach — descent rate, airspeed, flap management — and you have not done a thorough scan of the pattern for other traffic in the last 60 seconds.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before the scenario unfolds — what do you know about midair collision risk in a busy VFR pattern? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR15MA243A (2015, fatal): A Cessna 172 and an experimental North American Rockwell Sabreliner collided in midair approximately 1 mile northeast of Brown Field Municipal Airport during VFR traffic pattern operations. The local controller failed to properly identify the aircraft in the pattern and ensure control instructions were being performed before turning the Sabreliner into the Cessna's path. The controller's incomplete situational awareness was due to high workload at the time. The Cessna pilot did not maintain adequate visual lookout for known traffic in the pattern. Both aircraft were destroyed; both pilots were killed.
NTSB ERA14FA459A (2014, fatal): A Cessna 172M and an experimental Searey XLS collided in midair approximately 2 miles southeast of Buffalo-Lancaster Regional Airport during local EAA Young Eagles event flights. The Cessna pilot failed to maintain adequate visual lookout for known traffic in the fly-in event traffic pattern. The Searey pilot also failed to see and avoid. Both aircraft were destroyed; both pilots were killed.
NTSB WPR13FA211B (2013, fatal): A Cessna 172RG and a Cessna 172M collided in midair approximately 3 miles southwest of Calabasas, California during local instructional and personal flights. The failure of the pilots in both aircraft to maintain adequate visual lookout resulted in a midair collision. Both aircraft were destroyed; both pilots were killed.
NTSB MIA03FA007A (2002, fatal): Two Cessna 172 instructional aircraft collided in cruise flight near Coral Springs, Florida. The failure of the dual students and flight instructors on both aircraft to see and avoid each other during training operations in the same practice area resulted in a midair collision. One aircraft was destroyed; the other sustained substantial damage. Both pilots were killed.
The real accidents cited above occurred at other airports — NOT at Lakeland Linder International Airport (KLAL). KLAL has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 23.7%, LOSS_OF_CONTROL_GROUND 19.4%, FORCED_LANDING 17.2%, HARD_LANDING 11.8%, RUNWAY_EXCURSION 8.6%), but these specific midair collision events happened at Brown Field, Buffalo-Lancaster, Calabasas, and Coral Springs. The scenario is localized to KLAL to make the pattern environment and traffic conflict real for you as a student here.
The consistent thread across all these events: the see-and-avoid requirement of 14 CFR §91.113 is the pilot's primary collision-avoidance tool in VFR. ATC provides traffic advisories in Class D (like KLAL), but separation is NOT guaranteed. A busy pattern, high controller workload, and incomplete situational awareness on the ground are documented factors. The pilot's responsibility is to maintain a continuous visual scan of the pattern, confirm spacing with other aircraft, and go around if a conflict develops. The NTSB data is clear: pilots who go around early avoid the accidents that kill pilots who continue a marginal approach.
The regional crosswind precedents (GAA17CA105, ERA21LA119, GAA19CA170) show that gusting crosswind conditions at the limits of the aircraft's demonstrated capability can degrade directional control during landing rollout. The Cessna 172M is demonstrated for 12 knots crosswind; gusts to 18 knots are at or beyond that limit. Recognize when conditions exceed your personal minimums and go around rather than fighting the airplane on the runway.
Key lesson — In a busy VFR pattern at a towered airport like KLAL, the pilot's see-and-avoid responsibility is not optional. Maintain a continuous visual scan of the pattern, confirm spacing with other aircraft, and do not hesitate to go around if a conflict develops or if you are uncomfortable with the approach. ATC provides traffic advisories, but separation is not guaranteed. A go-around is not a failure — it is the correct response to a marginal or conflicted approach. Additionally, recognize when gusting crosswind conditions exceed the aircraft's demonstrated capability or your personal minimums, and go around rather than fighting the airplane during landing rollout.
Debrief — teaching points
14 CFR §91.113 requires see-and-avoid in VFR — that is the pilot's primary collision-avoidance tool.
In Class D airspace like KLAL, ATC provides traffic advisories and sequencing, but separation is NOT guaranteed. The pilot is responsible for seeing and avoiding other aircraft. A continuous visual scan of the pattern — base leg, downwind, and final — is essential. A 60-second gap in scanning leaves a collision window. The NTSB data from WPR15MA243A, ERA14FA459A, WPR13FA211B, and MIA03FA007A all cite pilot failure to maintain adequate visual lookout as a contributing factor. Scan the pattern every 20–30 seconds, especially in a busy pattern.
Controller errors — incomplete situational awareness, high workload, failure to identify aircraft — are documented factors in midair collisions.
In WPR15MA243A, the local controller's high workload led to incomplete situational awareness and a failure to properly identify aircraft in the pattern before issuing a turn instruction that put two aircraft on a collision course. Do not assume ATC has complete awareness of all traffic. If you are unsure about a clearance or a go-around instruction, ask for clarification. If you sense a conflict, go around — do not rely solely on ATC to keep you safe.
A go-around is the correct response to a marginal or conflicted approach — it is not a failure.
The NTSB data shows that pilots who go around early in a marginal approach avoid the accidents that kill pilots who continue. If you see traffic on final ahead of you, if you are unsure about spacing, if you hear a go-around instruction and are not sure if it is for you, or if you are uncomfortable with the approach for any reason, go around. Advance throttle to full power, retract flaps to 0°, climb out on the downwind heading (090° for Runway 10 at KLAL), and advise the tower. The tower will re-sequence you. A go-around costs a few minutes; a collision costs lives.
Gusting crosswind conditions at the limits of demonstrated capability degrade directional control during landing rollout.
The Cessna 172M is demonstrated for 12 knots crosswind. Gusts to 18 knots are at or beyond that limit. The regional precedents (ERA21LA119, GAA19CA170) show that pilots who lose directional control in gusting crosswinds during rollout veer off the runway. Recognize when conditions exceed the aircraft's demonstrated capability or your personal minimums. If the gusts are marginal, go around rather than fighting the airplane on the runway. Use proper crosswind landing technique (upwind wing down, opposite rudder) and be ready to go around if control becomes marginal.
Do not maneuver aggressively at low altitude to avoid traffic — go around instead.
If you sense a traffic conflict at low altitude (below 500 ft AGL), the correct response is to go around, not to slip, bank hard, or otherwise maneuver aggressively. Low-altitude maneuvering in a gusting crosswind can lead to a stall/spin, as documented in the loss-of-control accidents. A go-around at 500 ft AGL is safe; a stall/spin at 200 ft AGL is fatal. The NTSB data from WPR13FA211B and MIA03FA007A show pilots maneuvering at low altitude to avoid traffic and losing control. Do not be that pilot.
Confirm spacing with ATC if you are unsure — ask the tower to confirm that spacing is adequate.
If you see traffic on final ahead of you and you are not sure about the spacing, call the tower and ask: 'KLAL Tower, [N-number], confirming spacing on the traffic on final — do you want me to adjust my descent or request a slight delay?' The tower will confirm or issue a go-around instruction. Explicit confirmation is better than assumption. The tower's response will give you the information you need to make a safe decision.
Built from the real accident record
Scenario built from NTSB WPR15MA243A (2015 midair collision, controller failure to identify aircraft in pattern), ERA14FA459A (2014 midair collision, pilot failure to maintain visual lookout in fly-in event), WPR13FA211B (2013 midair collision, dual pilot failure to see and avoid), and MIA03FA007A (2002 midair collision near Coral Springs, FL). Localized to KLAL with regional crosswind precedents GAA17CA105, ERA21LA119, GAA19CA170.
NTSB reports: WPR15MA243A · ERA14FA459A · WPR13FA211B · MIA03FA007A · GAA17CA105 · ERA21LA119 · GAA19CA170
ACS tasks: PA.I.F — Weather Information · PA.II.D — Approach and Landing · PA.II.E — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.III.B — Communication
Relevant FARs: §91.3 · §91.111 · §91.113 · §91.185
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 172M scenarios · More scenarios at KLAL