Carl Bingham/Motorsport Images
Hamilton summoned over jewelry breach
Lewis Hamilton has been summoned to the stewards at the Singapore Grand Prix for an alleged breach of an FIA International Sporting Code article that relates to jewelry.
The topic of drivers wearing jewelry was regularly discussed with the FIA earlier this season, with Hamilton feeling he was being specifically targeted by a clampdown of an existing regulation.
While agreements appeared to have been reached that avoided punishments, Hamilton has now been called to the stewards for an alleged breach of Appendix L, Chapter III of the FIA International Sporting Code.
Chapter III relates to helmets, flame-resistant clothing, frontal head restraints, safety belts or wearing of jewelry. The later article states: “The wearing of jewelry in the form of body piercing or metal neck chains is prohibited during the competition and may therefore be checked before the start.”
Hamilton, who has multiple piercings that he has been removing at recent races, has to visit the stewards with just over an hour to go before qualifying in Singapore.
Chris Medland
While studying Sports Journalism at the University of Central Lancashire, Chris managed to talk his way into working at the British Grand Prix in 2008 and was retained for three years before joining ESPN F1 as Assistant Editor. After three further years at ESPN, a spell as F1 Editor at Crash Media Group was followed by the major task of launching F1i.com’s English-language website and running it as Editor. Present at every race since the start of 2014, he has continued building his freelance portfolio, working with international titles. As well as writing for RACER, his broadcast work includes television appearances on F1 TV and as a presenter and reporter on North America's live radio coverage on SiriusXM.
Read Chris Medland's articles
Latest 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.