Impact on Climb-Out
Bird strike on departure from Brooksville–Tampa Bay Regional Airport — damage assessment, control authority, and the decision to return or continue
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Runway 09, on a local practice flight. Elevation 76 ft MSL. The runway is 7,001 ft of concrete, oriented 090°/270° (true). Wind is 080° at 12 knots, gusting to 18 — a 10-knot crosswind component on Runway 09. Visibility 10 SM, clear skies, scattered cumulus at 3,500 ft. It is mid-morning in late spring; wildlife activity is moderate to high.
You are a commercial pilot with roughly 800 hours total, 120 hours in the Cessna 182 Skylane. You are current and proficient. The 182 is a high-performance single — 230 hp Continental O-470 carbureted engine, constant-speed prop, cowl flaps, fixed gear, fuel selector BOTH. You have the high-performance endorsement. The airplane is within limits, full fuel, and has been thoroughly preflight-checked.
You are cleared for takeoff on Runway 09. You advance the throttle smoothly, manage the constant-speed prop to 2,000 RPM during the takeoff roll (the prop governor will maintain RPM as you accelerate), and rotate at 50 KIAS (Vr). The nose comes up cleanly. You are at 200 ft AGL, climbing at 80 KIAS (Vy, best rate of climb), heading 090°, when you hear a loud THUMP and feel a sharp jolt through the airframe. The left wing dips slightly. Immediately, the airspeed indicator flickers — a momentary fluctuation — and you feel a subtle but definite change in the airplane's handling. The left wing feels heavier, less responsive.
You have struck a large bird — likely a goose or heron from the nearby wetlands. The impact was on the left wing, somewhere near the leading edge. The airplane is still flying, still climbing, but the control feel has changed. You are at 250 ft AGL, still in the climb-out corridor off Runway 09 (heading 090°). The off-field environment ahead is mostly open developed (parks, large lots) and pasture — good forced-landing terrain if needed. Behind you is the runway. Ahead is the climb-out corridor toward the Tampa Class B airspace (ceiling 6,000 MSL, 1.5 nm away horizontally).
You have seconds to assess: Is the airplane still controllable? Is there visible damage? Can you continue the climb, or do you need to return to KBKV immediately? The tower is watching; they saw the strike on radar and heard the impact on the radio. They are waiting for your status.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'C182'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we enter the decision tree — what do you know about bird strikes in the Cessna 182? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB GAA19CA086 (2018): A Cessna 182 on a practice instrument approach sustained a bird strike to the left wing approximately 1 mile from the runway. The aircraft landed safely with substantial wing damage. The pilot assessed the damage, returned to the airport, and executed a safe landing. The probable cause was the collision with a bird, but the outcome was survivable because the pilot recognized the damage, returned to a known field, and executed a deliberate approach.
NTSB GAA16CA196 (2016): A Cessna 182 on an aerial observation flight struck a goose during cruise flight at approximately 2,000 feet MSL, shattering the windscreen. The pilot continued to the nearest airport and landed without further incident. The probable cause was the collision with a bird, but the outcome was survivable because the pilot maintained control authority and reached a safe landing area.
NTSB GAA16CA101 (2016): A Cessna 182 conducting aerial observation struck a buzzard during a left turn to avoid the bird. The accident resulted from an inadvertent collision with the bird while maneuvering during the aerial observation flight. The lesson: maneuvering to avoid a bird at low altitude can be more dangerous than accepting the strike.
NTSB CEN14CA095 (2013): A Cessna 182N struck a large bird (possibly an eagle or vulture) on the right wing leading edge during low-altitude flight over a bayou canal. The pilot successfully returned to a larger airport and landed without further incident despite substantial wing damage. The probable cause was the collision with a bird, but the outcome was survivable because the pilot recognized the damage, returned to a known field, and executed a safe landing.
Regional crosswind loss-of-control precedents: NTSB GAA17CA105 (2016 PA-46), ERA21LA119 (2021 C172R), and GAA19CA170 (2019 PA-11 tailwheel) all show that loss of directional control during landing rollout in gusting crosswind conditions is a real and recurring accident pattern. The common thread: pilots who recognize that crosswind conditions exceed their control authority and commit to a go-around or diversion early survive; pilots who fight deteriorating control during rollout do not.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history (field dominant patterns: HARD_LANDING 26.9%, FORCED_LANDING 11.5%, RUNWAY_EXCURSION 11.5%), but these specific bird-strike events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: a bird strike at low altitude is survivable if you assess the damage, return to a known field, and execute a deliberate approach. The C182 is a robust airplane — substantial wing damage is survivable if you maintain control authority and land on a runway. The danger is in delaying the return, attempting to climb to altitude with degraded control authority, or fighting a marginal crosswind landing with a damaged wing. The right decision is always: assess, return, land.
Key lesson — A bird strike at low altitude in the Cessna 182 is survivable if you assess the damage, return to a known field, and execute a deliberate approach. The off-field environment off Runway 09 at KBKV is good (pasture and open developed areas), but a runway landing is always preferable when the airplane is still controllable. If control authority is critically degraded, a controlled forced landing in good terrain is the right decision. The C182's constant-speed prop and cowl flaps are automatic — focus on airspeed management (best glide 70 KIAS) and control authority assessment. A crabbed approach and landing is the right technique for a crosswind landing with a damaged wing — it avoids stressing the damaged structure with cross-control inputs.
Debrief — teaching points
A bird strike at low altitude is survivable if you assess the damage and return to a known field.
The NTSB bird-strike accidents in the C182 show a consistent pattern: pilots who assess the damage, return to a known field, and execute a deliberate approach survive. The key is early recognition that something is wrong (a loud thump, a change in control feel, a momentary airspeed fluctuation) and immediate action to return to the airport. At 250 ft AGL, you have seconds to decide — but the decision is simple: return to the runway you know. Do not attempt to climb to altitude with a damaged wing; do not divert to an unfamiliar field if the home field is within gliding distance. Return, land, and let the mechanics assess the damage.
A change in control feel after a bird strike is a red flag for structural damage.
In this scenario, the left wing felt heavier and less responsive after the strike. That is the signal: the wing is damaged. The aileron is less effective, the wing is not generating lift as effectively, and the airplane's handling has changed. Do not ignore this signal. Do not continue climbing and hoping the damage will improve. Return to the airport immediately. The control authority you have at 250 ft AGL is the control authority you will have at 1,000 ft AGL — it does not improve with altitude. If anything, it degrades as the airplane climbs and the wing is asked to generate more lift.
Best glide in the C182 is 70 KIAS — establish this speed immediately after a bird strike.
Best glide speed for the C182 is 70 KIAS. This is the speed that maximizes glide distance and gives you the most time and distance to manage the emergency. After a bird strike, reduce power and establish 70 KIAS immediately. This speed is slower than cruise, which reduces the stress on the damaged wing. It is also the speed you would fly if the engine quit — so it is the safe default speed for any emergency descent.
A crabbed approach and landing is the right technique for a crosswind landing with a damaged wing.
When landing with a damaged wing in a crosswind, a crabbed approach (nose into the wind, tracking the runway centerline) is better than a wing-low approach. The crab keeps the damaged wing level and avoids cross-control inputs (aileron and rudder in opposite directions) that would stress the damaged structure. A wing-low approach requires aileron and rudder in opposite directions — if the damaged wing is on the inside of the turn, this stresses the wing further. The crab is the safer technique: nose into the wind, track the runway, and straighten the nose with rudder as you decelerate. This is the right call for any crosswind landing, but it is especially important with a damaged wing.
At KBKV, the off-field environment off Runway 09 is good — pasture and open developed areas — but a runway landing is always preferable.
The off-field environment off Runway 09's climb-out corridor (heading 090°) is good: mostly pasture/hay, open developed areas (parks, large lots), and medium development. If the engine quits or control authority is lost, you have good forced-landing terrain ahead. However, a runway landing is always preferable when the airplane is still controllable. The runway is 7,001 ft long — plenty of length for a firm landing with a damaged wing. Only consider a forced landing in open terrain if control authority is so degraded that you cannot safely execute a runway approach.
Recognize when control authority is critically degraded and commit to a forced landing instead of attempting a marginal turn back to the runway.
The regional crosswind loss-of-control precedents (GAA17CA105, ERA21LA119, GAA19CA170) show a consistent pattern: pilots who recognize that control authority is marginal and commit to a go-around or forced landing early survive; pilots who fight deteriorating control and attempt marginal maneuvers do not. At 1,000 ft AGL with barely responsive controls, a turn back to the runway is a high-risk maneuver. A controlled descent to good forced-landing terrain is the safer option. The lesson: know your limits, recognize when you are approaching them, and commit to the safer option early.
Built from the real accident record
Scenario built from NTSB GAA19CA086 (2018 C182 bird strike to left wing on approach), GAA16CA196 (2016 C182 goose strike / windscreen damage), GAA16CA101 (2016 C182 buzzard strike during turn), CEN14CA095 (2013 C182N large bird strike to wing leading edge). Regional crosswind/loss-of-control precedents: GAA17CA105 (2016 PA-46 crosswind loss of control), ERA21LA119 (2021 C172R crosswind landing), GAA19CA170 (2019 PA-11 tailwheel crosswind loss of control). Real events occurred at other airports — NOT at Brooksville–Tampa Bay Regional (KBKV).
NTSB reports: GAA19CA086 · GAA16CA196 · GAA16CA101 · CEN14CA095 · GAA17CA105 · ERA21LA119 · GAA19CA170
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight · PA.V.A — Preflight Inspection · PA.VI.C — Takeoff and Climb Performance
Relevant FARs: §91.3 · §91.13 · §91.185 · §61.31
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 KBKV