Advertisement
Green flag waving at accident scene at time of Bianchi crash, amateur video shows
By alley - Oct 6, 2014, 12:37 PM ET

Green flag waving at accident scene at time of Bianchi crash, amateur video shows

Although

the FIA noted that double waved yellow flags had been displayed

after Adrian Sutil's accident at the Japanese Grand Prix to act as a warning for drivers, amateur video has surfaced of the ensuing incident in which Jules Bianchi suffered severe head injuries showing that a green flag was waved at the marshal post prior to and even after Bianchi's collision with the tractor that was removing Sutil's Sauber. The green flag is shown to inform drivers that they may accelerate once clear of the accident scene but, given

the fading light that Sutil, among others, reckoned to have played a role in the incident

, it is possible that it could have been misinterpreted.

The video graphically illustrates the high-speed nature of the impact – estimated via telemetry at 132mph – which lifted the tractor off the ground and demolished the left side of Bianchi's Marussia.

Former world champion

Jacques Villeneueve called Monday for F1 to standardize its safety car practices in the event of any on-course incident

.

Click here to view the video. WARNING: Contains accident footage that may be disturbing to some viewers.

UPDATE:

Jalopnik.com obtained this alternate view of the incident

, along with this explanation of the green flag offered by a frequent track marshal:

"The green flag is at the station AFTER the incident, which is per protocol –  they had not yet deployed the safety car (single standing yellow + SC board all around the track) and were handling the Sutil car under a local yellow, following standard protocol. The station upstream is showing waved double-yellow (per FIA standard) as is correct."

  • F1: Marussia asks for patience over Bianchi news

 

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.