The UCI confirmed on Wednesday, December 13, that Chris Froome (Team Sky) was notified of an adverse analytical finding (AAF) for salbutamol in excess of 1,000 nanograms per millilitre (ng/ml) in a sample collected during the Vuelta a España this September 7, an event where he went on to win the overall title.
Froome was notified of the AAF on September 20, the same day he finished third in the elite men's time trial at the UCI Road World Championships in Bergen.
The analysis of the B sample confirmed the results of the rider's A sample to have 2,000ng/ml of salbutamol, twice WADA's threshold limit, and the proceedings are being conducted in line with the UCI Anti-Doping Rules, according to a statement from the UCI.
ADVERTISEMENT
Froome has said previously that he suffered from asthma since he was a child and has used inhalers during his career. He explained that his symptoms worsened during the Vuelta, and he sought medical advice from the team doctor in order to increase his salbutamol dosage. Team Sky principal David Brailsford said the team will co-operate with the UCI to establish the cause of Froome's elevated concentration.
The World Anti-Doping Agency has regulations around the use of salbutamol, a bronchodialator (beta 2-agonist) used to treat asthma.
The medication is strictly prohibited in oral and injectable forms. When used to treat asthmatic symptoms via an inhaler, however, WADA's prohibited list provides that "the presence in urine of salbutamol in excess of 1000 ng/mL or formoterol in excess of 40 ng/mL is presumed not to be an intended therapeutic use of the substance and will be considered as an Adverse Analytical Finding (AAF) unless the Athlete proves, through a controlled pharmacokinetic study, that the abnormal result was the consequence of the use of the therapeutic dose (by inhalation) up to the maximum dose indicated above."
You can read more at Cyclingnews.com
via Cyclingnews Latest News http://www.cyclingnews.com/news/timeline-of-chris-froomes-adverse-analytical-finding-for-salbutamol
No comments:
Post a Comment