10
JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include all the rules used to determine Aerodrome Operating Minima (AOM) according to JAR-OPS, but shows the applicable tables. The JAR- OPS rules have been adopted by the Committee of Joint Aviation Authorities (JAA) on 28 March 1995 and are still used in some countries, even the JAA do not exist any longer. MET VISIBILITY/RVR CONVERSION JAR-OPS AOM are generally expressed in RVR. If only meteorological visibility is reported, the charted RVR value can be substituted by reported meteorological VIS for straight-in instrument approaches as shown in Table 1. Note: Table 1 shall not be applied for calculating Take-off or Category II/III minimums or when a reported RVR is available. TAKE-OFF MINIMUMS a. For multi-engine aircraft, whose performance is such that in the event of a critical power unit failure at any point during take-off the aircraft can either stop or continue the take-off to a height of 1500ft above the aerodrome while clearing all obstacles by the required margins, the take-off minimums established by an operator must be expressed as RVR/VIS values not lower than those in Table 2 below. b. For multi-engine aircraft whose performance is such that they cannot comply with the performance conditions specified in paragraph a. above in the event of a critical power unit failure, there may be a need to re-land immediately and to see and avoid obstacles in the take-off area. Such aircraft may be operated to take-off minimums shown in Table 3. The take-off minimums established by an operator must be based upon the height from which the one engine inoperative net take-off flight path can be constructed. The RVR/VIS minimums used may not be lower than either those specified in Table 2 or 3.

JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

  • Upload
    others

  • View
    60

  • Download
    1

Embed Size (px)

Citation preview

Page 1: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

JAR-OPS 1 & JAR-OPS 3

JAR-OPS 1 (Aeroplane) GENERAL

The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include all the rules used to

determine Aerodrome Operating Minima (AOM) according to JAR-OPS, but shows the applicable tables. The JAR-

OPS rules have been adopted by the Committee of Joint Aviation Authorities (JAA) on 28 March 1995 and are still

used in some countries, even the JAA do not exist any longer.

MET VISIBILITY/RVR CONVERSION

JAR-OPS AOM are generally expressed in RVR. If only meteorological visibility is reported, the charted RVR value can

be substituted by reported meteorological VIS for straight-in instrument approaches as shown in Table 1.

Note: Table 1 shall not be applied for calculating Take-off or Category II/III minimums or when a reported RVR is

available.

TAKE-OFF MINIMUMS

a. For multi-engine aircraft, whose performance is such that in the event of a critical power unit failure at any point during take-off the aircraft can either stop or continue the take-off to a height of 1500ft above the aerodrome while clearing all obstacles by the required margins, the take-off minimums established by an operator must be expressed as RVR/VIS values not lower than those in Table 2 below.

b. For multi-engine aircraft whose performance is such that they cannot comply with the performance conditions specified in paragraph a. above in the event of a critical power unit failure, there may be a need to re-land immediately and to see and avoid obstacles in the take-off area. Such aircraft may be operated to take-off minimums shown in Table 3. The take-off minimums established by an operator must be based upon the height from which the one engine inoperative net take-off flight path can be constructed. The RVR/VIS minimums used may not be lower than either those specified in Table 2 or 3.

Page 2: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

LOW VISIBILITY TAKE-OFF A take-off on a runway where the RVR is less than 400m. An operator shall:

- Verify that Low Visibility Procedures have been established and are in force where low visibility operation are to be conducted.

- Establish procedures and instructions for Low Visibility Take-off operations.

Subject to the approval of the Authority, and provided the requirements in paragraphs a to e below have been satisfied, an operator may reduce the take-off minimums shown in Table 2 for CAT A, B & C aircraft to RVR 125m and for CAT D aircraft to RVR 150m when:

a. low Visibility Procedures are in force; b. high intensity CL spaced 15m or less and HIRL spaced 60m or less are in operation; c. crews have satisfactorily completed training in a simulator approved for this procedure; d. a 90m visual segment is available from the cockpit at the start of the take-off run; e. the required RVR value has been achieved for all of the relevant RVR reporting points.

USING AN APPROVED LATERAL GUIDANCE SYSTEM Subject to approval of the Authority, an operator of an aircraft using an approved lateral guidance system may reduce the take-off minimums shown in Table 2 for CAT A, B & C aircraft to less than RVR 125m and for CAT D aircraft to less than RVR 150m; but not lower than RVR 75m provided runway protection and facilities equivalent to Category III landing operations are available.

Page 3: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

CIRCLE-TO-LAND MINIMUMS

An operator must ensure that the MDH and visibility for the aircraft category concerned is not below the values shown in Table 4 below and any existing State minimum.

VISUAL APPROACH An operator shall not use a RVR of less than 800m for a visual approach.

NON-PRECISION APPROACH MINIMUMS

An operator must ensure that the MDH for a non-precision approach is not below the OCH/OCL for the category of aircraft or the MDH values given in Table 5.

The lowest possible RVR (if no higher State minimum exist) to be used by an operator for non-precision approaches is shown in Table 6 below. The table is only applicable to conventional approaches with a nominal descent slope of not greater than 4 degrees (7.0%). Greater descent slopes will usually require that visual glide slope guidance (e.g., PAPI) is also visible at the MDH. The figures may be either reported RVR or meteorological VIS converted to RVR. NOTE: The MDH in Table 6 refers to the initial calculation of MDH. When selecting the associated RVR, there is no need to take account of a rounding up to the nearest 10ft, which may be done for operational purposes, e.g., conversion to MDA.

Page 4: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

PRECISION APPROACH (CAT I) MINIMUMS

A CAT I operation is a precision approach and landing using an ILS, MLS or PAR with a DH not lower than 200ft and with a RVR not less than 550m. The lowest possible RVR (if no higher State minimum exist) to be used by an operator for a CAT I approach is shown in Table 7 below. The table is only applicable to conventional approaches with a glide slope angle up to and including 4 degrees. The figures may be either reported RVR or meteorological VIS converted to RVR. NOTE: The DH in Table 7 refers to the initial calculation of a DH. When selecting the associated RVR, there is no need to take account of a rounding up to the nearest 10ft, which may be done for operational purposes, e.g., conversion to DA.

Page 5: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

PRECISION APPROACH (CAT II) MINIMUMS

A CAT II operation is a precision instrument approach and landing using an ILS or MLS with a decision height below 200ft but not lower than 100ft, and a minimum RVR of 300m. The lowest possible RVR (if no higher State minimum exist) to be used by an operator for CAT II approaches is shown in Table 8 below.

Page 6: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

PRECISION APPROACH (CAT III) MINIMUMS

NOTE: Where the DH and RVR do not fall within the same category, the RVR will determine in which category the operation is to be considered.

PLANNING MINIMUMS (IFR Flights)

Page 7: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

EFFECT ON AOM OF TEMPORARILY FAILED OR DOWNGRADED GROUND EQUIPMENT

These procedures/instructions are applicable for both pre-flight and in flight situations. It is not expected that the commander consults these instructions after passing the OM or an equivalent position. If failure of ground equipment, other than the primary approach aid in use, occurs at such a late stage, the approach may be continued at commander’s discretion. If failures are known before this stage, the effect on the approach must be considered by using the following table; that means, minimums must be increased and/or relevant procedures must be used.

Page 8: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

JAR-OPS 3 (Helicopter)

TAKE-OFF MINIMUMS

Table – RVR/VIS for take-off

Onshore heliports with IFR departure procedure RVR/VIS

No lighting and no markings (Day) 250m or the rejected take-off distance,

whichever is greater

No markings (night) 800m

Runway edge/FATO lighting and centerline marking 200m

Runway edge/FATO lighting, centerline marking and RVR information

150m

Offshore Helideck

Two pilot operations 250m (1)

Single pilot operations 500m (1)

(1) The commander must establish that the take-off flight path is free of obstacles.

CIRCLE-TO-LAND MINIMUMS

For circling the specified MDH shall not be less than 250ft and the meteorological visibility shall not be less than

800m. This includes also Visual manoeuvering (circling) with prescribed flight tracks.

An operator shall not use an RVR of less than 800m for a visual approach.

Lighting

Full facilities comprise FATO/runway markings, 720m or more of HI/MI approach lights, FATO/runway edge lights,

threshold lights and FATO/runway end lights. Lights must be on.

Intermediate facilities comprise FATO/runway markings, 420 - 719m of HI/MI approach lights, FATO/runway edge

lights, threshold lights and FATO/runway end lights. Lights must be on.

Basic facilities comprise FATO/runway markings, <420m of HI/MI approach lights or any length of LI approach lights,

FATO/runway edge lights, threshold lights and FATO/runway end lights. Lights must be on.

Nil approach lights facilities comprise FATO/runway markings, FATO/runway edge lights, threshold lights,

FATO/runway end lights or lights at all.

Page 9: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

NON-PRECISION APPROACH MINIMUMS

Table – Onshore non-precision approach minima

MDH (ft) Full Facilities

RVR (m)

Intermediate Facilities RVR (m)

Basic Facilities RVR (m)

Nil RVR (m)

250 - 299 600 800 1000 1000

300 - 449 800 1000 1000 1000

450 and above 1000 1000 1000 1000

The above figures are either reported RVR or meteorological visibility converted to an RVR. The MDH refers to the

initial calculation of MDH. There is no need to take account of rounding.

PRECISION APPROACH (CAT I) MINIMUMS

Table – Onshore Precision Approach Minima Category I

DH (ft) Full Facilities

RVR (m)

Intermediate Facilities RVR (m)

Basic Facilities RVR (m)

Nil RVR (m)

200 500 600 700 1000

201 – 250 550 650 750 1000

251 - 300 600 700 800 1000

301 and above 750 800 900 1000

The above figures are either reported RVR or meteorological visibility converted to an RVR. The DH refers to the

initial calculation of DH. There is no need to take account of rounding.

Page 10: JAR-OPS 1 & JAR-OPS 3 - Code 7700 · JAR-OPS 1 & JAR-OPS 3 JAR-OPS 1 (Aeroplane) GENERAL The following is an excerpt based on JAR-OPS 1 Subpart D and E. The excerpt does not include

PRECISION APPROACH (CAT II) MINIMUMS

Decision height (ft) Auto-coupled to below DH

RVR (m)

100 – 120 300

121 – 140 400

141 and above 450

PLANNING MINIMUMS

Type of Approach Planning Minima

CAT II and III CAT I RVR

CAT I DH plus 200ft

RVR/VIS plus 400m

Non-precision MDH plus 200ft

RVR/VIS plus 400m Ceiling at or above MDH