Registration Dossier

Data platform availability banner - registered substances factsheets

Please be aware that this old REACH registration data factsheet is no longer maintained; it remains frozen as of 19th May 2023.

The new ECHA CHEM database has been released by ECHA, and it now contains all REACH registration data. There are more details on the transition of ECHA's published data to ECHA CHEM here.

Diss Factsheets

Categories

Categories

Category name:
Isomerised olefins including branched, linear, alpha, and internal, predominantly one carbon number

Justifications and discussions

Category definition:
Isomerised Olefins with Predominantly One Carbon Number
Category rationale:
The Isomerised Olefins category covers products that are comprised of a single carbon number that may contain various isomers. As the category name implies, these materials are all olefins. The position of the double bond may vary and the carbon chain may be either linear, branched or a mix of both. The category covers a carbon range of C6 to C20. The phys-chem and environmental fate properties of the category members will be similar or if they change they will change in a predictable fashion. For example, the water solubility is expected to decrease as the carbon number increases. Environmental effects will behave in a similar manner, acting via non-polar narcosis. It is expected that the low water solubility will limit the potential aquatic toxicity of the higher carbon number members. With regard to mammalian endpoints, category members are liquids of moderate to low volatility. Skin contact therefore represents the primary route of exposure with inhalation expected to be only a minor or secondary source of exposure. The one possible exception would be the hexenes which has moderately volatility. The category members differ from one-another only in carbon chain length. The differing carbon chain length, position of the double bond and presence of branching is not anticipated to have a significant effect on the mammalian toxicity. It can therefore, be assumed that products meeting the applicable domain will behave in a similar manner and that use of read-across is valid.