Light
Dark
System
Log In
Loading...
Compare / EASA/
Incorporated Amendments
/
Compare & Highlight Differences
GM1 HPT-DSN.B.100 Final approach and take-off areas (FATOs)
Available versions for ERULES-1963177438-12359
ED Decision 2019/012/R
found in: Aerodromes (139/2014) Part-ADR.AR Part-ADR.OR Part-ADR.OPS CS-ADR-DSN CS-HPT-DSN (Dec 2024)
From
Easy Access Rules ... (Mar 2026)
Aerodromes (139/20... (Dec 2024)
Aerodromes (139/20... (Jun 2023)
From section
To
Easy Access Rules ... (Mar 2026)
Aerodromes (139/20... (Dec 2024)
Aerodromes (139/20... (Jun 2023)
To section
No visible text changes
0 removals
0 additions
View
Rich
Plain
Sync scrolling
Share
From
Show details
Hide details
To
Show details
Hide details
Version
Show side by side
GM1 HPT-DSN.B.100 Final approach and take-off areas (FATOs) ED Decision 2019/012/R (a) General: (1) A FATO may not be necessary to be provided at and aerodrome, where the runway is used for the purposes of final approach and take-off of helicopters. (2) Where a FATO is located near a runway or taxiway, and when simultaneous helicopter and aeroplane operations are planned, the separation distance between the edge of a runway or taxiway and the edge of a FATO should not be less than the appropriate dimension in Table GM1-B-1. (3) Operational limitations should be considered under certain wind conditions. <table border="1" cellpadding="0" cellspacing="0" width="606"><tr><td valign="top" width="303"><p><b>If aeroplane mass and/or helicopter mass are</b></p></td><td valign="top" width="303"><p><b>Distance between FATO edge and runway edge or taxiway edge</b></p></td></tr><tr><td valign="top" width="303"><p>up to but not including 3 175 kg</p></td><td valign="top" width="303"><p>60 m</p></td></tr><tr><td valign="top" width="303"><p>3 175 kg up to but not including 5 760 kg</p></td><td valign="top" width="303"><p>120 m</p></td></tr><tr><td valign="top" width="303"><p>5 760 kg up to but not including 100 000 kg</p></td><td valign="top" width="303"><p>180 m</p></td></tr><tr><td valign="top" width="303"><p>100 000 kg and over</p></td><td valign="top" width="303"><p>250 m</p></td></tr><tr><td colspan="2" valign="top" width="606"><p>Note: The values specified in this table are primarily intended to mitigate risks of wake turbulence encounters. In addition to this table, when positioning a FATO intended to be used simultaneously with a nearby runway or taxiway, attention should be given to other CS ADR-DSN requirements such as the minimum runway strip width. Local environment should be taken into account when setting the separation between the FATO and nearby infrastructure elements to ensure the safety of simultaneous operations.</p></td></tr></table> Table GM1-B-1. FATO minimum separation distance (b) A FATO should not be located: (i) near taxiway intersections or holding points where jet engine efflux is likely to cause high turbulence; or (ii) near areas where aeroplane vortex wake generation is likely to occur.
GM1 HPT-DSN.B.100 Final approach and take-off areas (FATOs) ED Decision 2019/012/R (a) General: (1) A FATO may not be necessary to be provided at and aerodrome, where the runway is used for the purposes of final approach and take-off of helicopters. (2) Where a FATO is located near a runway or taxiway, and when simultaneous helicopter and aeroplane operations are planned, the separation distance between the edge of a runway or taxiway and the edge of a FATO should not be less than the appropriate dimension in Table GM1-B-1. (3) Operational limitations should be considered under certain wind conditions. <table border="1" cellpadding="0" cellspacing="0" width="606"><tr><td valign="top" width="303"><p><b>If aeroplane mass and/or helicopter mass are</b></p></td><td valign="top" width="303"><p><b>Distance between FATO edge and runway edge or taxiway edge</b></p></td></tr><tr><td valign="top" width="303"><p>up to but not including 3 175 kg</p></td><td valign="top" width="303"><p>60 m</p></td></tr><tr><td valign="top" width="303"><p>3 175 kg up to but not including 5 760 kg</p></td><td valign="top" width="303"><p>120 m</p></td></tr><tr><td valign="top" width="303"><p>5 760 kg up to but not including 100 000 kg</p></td><td valign="top" width="303"><p>180 m</p></td></tr><tr><td valign="top" width="303"><p>100 000 kg and over</p></td><td valign="top" width="303"><p>250 m</p></td></tr><tr><td colspan="2" valign="top" width="606"><p>Note: The values specified in this table are primarily intended to mitigate risks of wake turbulence encounters. In addition to this table, when positioning a FATO intended to be used simultaneously with a nearby runway or taxiway, attention should be given to other CS ADR-DSN requirements such as the minimum runway strip width. Local environment should be taken into account when setting the separation between the FATO and nearby infrastructure elements to ensure the safety of simultaneous operations.</p></td></tr></table> Table GM1-B-1. FATO minimum separation distance (b) A FATO should not be located: (i) near taxiway intersections or holding points where jet engine efflux is likely to cause high turbulence; or (ii) near areas where aeroplane vortex wake generation is likely to occur.
##### GM1 HPT-DSN.B.100 Final approach and take-off areas (FATOs) *ED Decision 2019/012/R* (a) General: (1) A FATO may not be necessary to be provided at and aerodrome, where the runway is used for the purposes of final approach and take-off of helicopters. (2) Where a FATO is located near a runway or taxiway, and when simultaneous helicopter and aeroplane operations are planned, the separation distance between the edge of a runway or taxiway and the edge of a FATO should not be less than the appropriate dimension in Table GM1-B-1. (3) Operational limitations should be considered under certain wind conditions. <table bgcolor="#d9d9d9" cellpadding="7" cellspacing="0"> <col/> <col/> <tr valign="top"> <td bgcolor="#808080"><p align="left"> <b>If aeroplane mass and/or helicopter mass are</b></p> </td> <td bgcolor="#808080"><p align="center"> <b>Distance between FATO edge and runway edge or taxiway edge</b></p> </td> </tr> <tr valign="top"> <td bgcolor="#d9d9d9"><p align="left"> up to but not including 3 175 kg</p> </td> <td bgcolor="#d9d9d9"><p align="center"> 60 m</p> </td> </tr> <tr valign="top"> <td bgcolor="#d9d9d9"><p align="left"> 3 175 kg up to but not including 5 760 kg</p> </td> <td bgcolor="#d9d9d9"><p align="center"> 120 m</p> </td> </tr> <tr valign="top"> <td bgcolor="#d9d9d9"><p align="left"> 5 760 kg up to but not including 100 000 kg</p> </td> <td bgcolor="#d9d9d9"><p align="center"> 180 m</p> </td> </tr> <tr valign="top"> <td bgcolor="#d9d9d9"><p align="left"> 100 000 kg and over</p> </td> <td bgcolor="#d9d9d9"><p align="center"> 250 m</p> </td> </tr> <tr> <td bgcolor="#d9d9d9" colspan="2" valign="top"><p> Note: The values specified in this table are primarily intended to mitigate risks of wake turbulence encounters. In addition to this table, when positioning a FATO intended to be used simultaneously with a nearby runway or taxiway, attention should be given to other CS ADR-DSN requirements such as the minimum runway strip width. Local environment should be taken into account when setting the separation between the FATO and nearby infrastructure elements to ensure the safety of simultaneous operations.</p> </td> </tr> </table> ***Table GM1-B-1. FATO minimum separation distance*** (b) A FATO should not be located: (i) near taxiway intersections or holding points where jet engine efflux is likely to cause high turbulence; or (ii) near areas where aeroplane vortex wake generation is likely to occur.