Overview
• Operator: Allegiant Air
• Aircraft Model: Airbus A320-200
• Registration: N253NV
• Flight Number: G4-1536
• Route: St. Petersburg (PIE) → Flint (FNT)
• Date: 11 March 2025
• Occupants: 182 people on board
• Incident Type: Bird Strike on Takeoff
• Outcome: Safe return to departure airport
• Investigation: FAA to conduct an inquiry
⸻
Incident Summary
Allegiant Air flight G4-1536 departed St. Petersburg’s runway 36, bound for Flint, Michigan, when the aircraft struck a bird during takeoff. The crew immediately reported the incident and decided to return to the airport after burning fuel.
The aircraft stopped its climb at 3,000 feet, entered a holding pattern in a left-hand downwind for runway 36, and landed safely 18 minutes after departure.
⸻
Sequence of Events
1. Takeoff & Bird Strike
• The aircraft took off normally from runway 36.
• Shortly after liftoff, the crew observed a bird strike on the runway.
• Airport operations later discovered bird remains near taxiway A4, matching the description of a large bird similar to a hawk.
2. Return Decision & Fuel Burn
• The crew decided to return to St. Petersburg as a precaution.
• They held at 3,000 feet to burn fuel before the approach.
3. Safe Landing & Taxi to Apron
• The aircraft landed safely on runway 36 about 18 minutes after departure.
• It taxied to the apron without further incident.
⸻
Investigation Findings & Initial Analysis
1. Bird Strike Location & Type
• The strike occurred on the runway during takeoff, with debris found near taxiway A4.
• The bird involved was large, likely a hawk or similar raptor species.
2. Aircraft Damage & Post-Landing Inspection
• The extent of damage is currently unknown, pending further inspection.
• The aircraft remained on the ground for at least 6 hours after landing.
⸻
Potential Causes & Contributing Factors
1. Presence of Large Birds Near Runway
• St. Pete-Clearwater Airport’s location may attract large birds, increasing the risk of strikes.
• Limited bird deterrence measures or sudden bird movement may have contributed.
2. Operational Decisions & Precautionary Return
• The crew made a cautious decision to return, avoiding potential in-flight issues.
• The holding pattern allowed for fuel burn, reducing landing risks.
⸻
Safety Recommendations & Future Prevention
1. Enhanced Bird Control Measures at St. Petersburg
• Regular wildlife monitoring & deterrence methods to reduce large bird presence near runways.
• Use of bioacoustics, falconry, or other wildlife control strategies to minimize risks.
2. Aircraft Inspection Protocols After Bird Strikes
• Mandatory post-strike inspections, particularly for engine and airframe damage.
• Borescope inspections for internal damage if birds are suspected of entering engines.
3. Pilot & ATC Coordination for Bird Strike Response
• Improved reporting protocols for bird activity near the airport.
• Enhancing ATC & pilot awareness of seasonal bird migration patterns.
⸻
Conclusion
Allegiant Air flight G4-1536 successfully returned to St. Petersburg after a bird strike, with no injuries or further complications. The crew handled the incident professionally, ensuring a safe landing.
The FAA will investigate the event, and the aircraft remains grounded for assessment. Enhanced wildlife management and strike prevention measures could further reduce such risks at the airport.
⸻
Disclaimer
“This report is based on available information as of 11 March 2025. While every effort has been made to ensure accuracy, the completeness of the details cannot be guaranteed. If you are the rightful owner of any referenced materials and wish them removed, please email takedown@cockpitking.com.”
