
Isack Hadjar's Bizarre Crash Triggers First Red Flag in Monaco FP1
Isack Hadjar's strange crash at the Swimming Pool section brought out the first red flag of the Monaco weekend, leaving Red Bull with a major repair job ahead of FP2.
Isack Hadjar caused the first red flag of the Monaco Grand Prix weekend during Friday's opening practice session, crashing his Red Bull in a bizarre incident at Turn 16 with less than 25 minutes remaining. The rookie driver hit the barrier nose-first on exit of the Swimming Pool chicane, then slid through the corner and into the wall before his car was spat back across the track, scattering debris.
Why it matters:
Monaco practice time is precious, and Hadjar's mistake not only cost Red Bull valuable track data but also left the team with a significant repair job before FP2. For a rookie still finding his feet, this error under the spotlight of Monaco's tight streets could weigh on his confidence. The timing is especially critical as the RB22 showed promising pace early in the session.
The details:
- The crash: Hadjar lost control on exit of Turn 16, making initial contact with the barrier before sliding through the chicane and into the wall on the opposite side. The impact sent the car and debris across the track, forcing the red flag.
- Radio reaction: The Red Bull driver immediately reported over the radio that the car had "snapped" and admitted he did not "understand" how the crash had happened.
- Session leader: Ferrari's Kimi Antonelli topped the timesheets when the red flag flew, with the session later resumed for a few minutes but no significant changes to the order.
- Damage: The left-rear corner of Hadjar's car appeared heavily damaged, and the team will need to thoroughly inspect the chassis and suspension before FP2.
What's next:
Red Bull's mechanics face a tight turnaround to repair the RB22 ahead of second practice, which kicks off later this afternoon. Hadjar will need to regroup quickly – Monaco's narrow layout leaves little margin for error, and any lingering hesitation could cost him more track time. The team will also analyze telemetry to understand if a mechanical issue contributed to the sudden snap.
Don't miss the next lap
Get the deep dives and technical analysis from the world of F1 delivered to your inbox twice a week.
Zero spam. Only high-octane analysis. Unsubscribe anytime.
Join the inner circle
Get the deep dives and technical analysis from the world of F1 delivered to your inbox twice a week.
Zero spam. Only high-octane analysis. Unsubscribe anytime.



