Advertisement
Advertisement
F1: FIA takes no action over Alonso crash
By alley - Mar 20, 2016, 6:31 AM ET

F1: FIA takes no action over Alonso crash

The Australian Grand Prix Formula 1 stewards have concluded that no blame should be apportioned in

the enormous crash involving Fernando Alonso and Esteban Gutierrez

.

Alonso's McLaren rolled through the Turn 3 gravel trap in Melbourne after clipping the rear of the Haas under braking. Both drivers were unhurt.

The stewards announced that the incident would be investigated after the race, but after talking to both drivers and teams and examining video evidence decided no penalties were necessary.

A statement said: "The stewards examined the evidence and conclude that no driver was wholly or predominately to blame."

  • Alonso didn't know where he'd landed after crash

Both drivers had described the crash as a racing incident and said their primary concern was for each other's well being afterward. Alonso dismissed suggestions that Gutierrez triggered it by changing line unexpectedly or braking early.

"If he did, it's because he tried to brake for his own racing line and I need to anticipate that as well," Alonso said. "But you are so focused on the slipstream, you only see a rear wing. You don't have any more vision of the track.

  • Button: Alonso crash no case against cockpit halo

"I took the slipstream in quite an extreme way and tried to overtake at the last moment. Probably I braked a little bit too late. It's a combination of things.

"We are both OK, that's the most important thing."


RACER's Formula 1 coverage is presented by Grand Prix Tours. Feel the power and the glory of Grand Prix racing now via Grand Prix Tours' Pick 8 competition.

Originally on Autosport.com

Crandon International Raceway announces first-ever vintage revival & reunion for 2026 Brush Run Speed Festival

Promo Image

Comments

Comments are disabled until you accept Social Networking Cookies. Update cookie preferences

If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.