Safety Assessments for non-EASA/ICAO compliant Runway Strip
Numerous airports have several deviations related to the provision of a Runway Strip. Most common deviations are non-frangible objects (buildings, antennas), parallel taxiways or tunnel entrances, fences, public roads or significant slopes in the strip. Above that temporary works involving construction equipment in the strip may cause safety issues.
A runway strip – and its graded portion – aims to “reduce the risk of damage to aircraft running off a runway, and to protect aircraft flying over it during take-off or landing operations” (ICAO Annex 14). Further requirements are introduced by ICAO Aerodrome Design Manual and EASA CS ADR-DSN (e.g. safe use by rescue and firefighting vehicles). On top of that, a large number of national regulations exists: German regulations - for instance - are more permissive than many others to allow construction works in some parts of the non-graded portion of the runway strip (provided that specific conditions are fulfilled).
airsight assisted in the last few years many airports and Civil Aviation Authorities in managing deviations from the above mentioned requirements, conducting on their behalf Safety Assessments and developing mitigating measures to reduce the risks following to the ALARP principles (As Low As Reasonably Practicable) when necessary.
airsight developed and maintain for such exercise a risk-model to quantify the probability of lateral excursion of an aircraft from the runway during take-off and landing. It enables the assessment of the individual risk level for different scenarios based on the local characteristics of each airport (e.g. type of approach, traffic mix, location of obstacles, etc.).
This “safety-based” approach, compliant with aviation regulations, enables airport operators to make informed decisions on the infrastructural or operational measures required to mitigate risks if necessary. Often this approach considerably reduces the investment required to ensure an acceptable level of safety when “full” compliance with infrastructure requirements is not possible or feasible.