LEVC AD 2 AERODROME DATA

1. START-UP OF ENGINES/JETS.

Note: This section uses abbreviations defined in ENR 1.5.

To avert the automatic cancellation of flight plans, the EOBT must be maintained up-to-date.

1. Permission to start up engines/jets shall be requested on the clearance frequency or, if this is not attended, on the frequency stated via ATIS or CLD message. When this permission is requested, the aircraft must be completely ready to start up immediately.

2. For requests by voice, pilots must indicate the full aircraft call sign to ATC, together with the stand occupied and the ATIS message received.

3. Start-up clearance shall be requested:

   • Aircraft without assigned CTOT: From 15 minutes prior to their EOBT, until 10 minutes after it if they are parked on stands with exit by towed push-back, or until 15 minutes after their EOBT for the remaining stands.

   • Aircraft with assigned CTOT: From 20 minutes prior to their CTOT until 10 minutes prior to their CTOT, if they are parked on stands with exit by towed push-back, or from 15 minutes prior to their CTOT to 5 minutes prior to their CTOT for the remaining stands.

   • To improve the predictability of the TTOT, ATC may issue instructions for start-up clearance to be requested at a specific time.

   • In periods of high demand, ATC may apply other values which guarantee compliance with the TW of the flight.

ATC CLEARANCE REQUEST AND START-UP VIA DATA LINK

DCL departure procedures are applied at Valencia Airport in the provision of ATC clearance and start-up services. For more information on the DCL service, see AIP ENR 1.5, section 3. DEPARTING FLIGHTS, ATC clearance and start-up via data link (DCL).

In the event of any discrepancy, voice communications will always prevail over data link.

The pilot may request ATC clearance via DCL no earlier than 30 minutes before the EOBT.

Approval of start-up jointly with ATC clearance will be facilitated provided that the parameters established in AD 2-LEVC, item 20, General taxiing procedures, 1.C, are satisfied.

• The pilot shall request ATC clearance and start-up simultaneously via RCD. The RCD message shall contain the following data:

  1. Call sign according to the submitted flight plan (FPL).

  2. Departure aerodrome.

  3. Parking position.

  4. Destination aerodrome.

  5. Letter of the ATIS information received.

  6. ICAO aircraft type.

Any free text sent via the RCD by the pilot will not be considered by ATC. Special requests shall always be made via voice communications.

• The pilot will receive a message of acceptance, "RCD RECEIVED", or of rejection, "RCD REJECTED".

When an RCD message is received earlier than the ranges established in AD 2-LEVC, item 20, General taxiing procedures, 1.C, the RCD will be accepted and the CLD will be sent with ATC clearance, asking the crew to call when the aircraft is ready and in accordance with their EOBT/CTOT.

When an RCD message is received within the ranges established in AD 2-LEVC, item 20, General taxiing procedures, 1.C, the RCD will be accepted and the CLD will be sent with ATC clearance and approval of start-up.

• In the case of acceptance, Valencia Clearance will issue a CLD message with the following fields:

1. Aircraft call sign.

2. Destination aerodrome.

3. Assigned runway for departure.

4. Departure procedure (SID). Note: The initial altitude will be that of the published SID.

5. SSR code mode A (SQUAWK).

6. ADT (Approved Departure Time). Note: ADT = CTOT of the flight, if applicable.

7. Next frequency.

8. Current ATIS information letter.

9. Additional information, which will include start-up clearance or instructions to request it if the start-up approval parameters indicated in AD 2-LEVC, item 20, 1.C, are not yet satisfied.

• When an FSM message of the type "REVERT TO VOICE PROCEDURES" is received, the data link communication will be deemed to have concluded and the revert to voice procedures will be applied.

• When the CLD message is received, the pilot:

1. If any inconsistency is detected in the received message, the pilot must revert to voice procedures and request a new clearance.

2. If the pilot considers the CLD clearance message to be correct, he/she must respond via data link with a CDA message.

3. If the pilot is not ready for start-up, he/she shall not accept the clearance and shall contact the controller by voice when ready.

• If a CDA message is not received by the pilot within the waiting time, or a CDA that is inconsistent with the previous CLD message is received, the data link communication will be terminated and a "CDA REJECTED" message will be received in the FMS.

• When a correct CDA message is received, the ATC system will send the aircraft a "CLEARANCE CONFIRMED" message in the FMS and will terminate the data link communication.

Push-back must be requested on the frequency stated in the appropriate CLD message, and it may only be approved via voice on that frequency.

REVERT TO VOICE PROCEDURES

Upon receiving a message of the type "REVERT TO VOICE PROCEDURES", or in the event of any inconsistency in the clearance received, the pilot will contact the controller by voice and request a new clearance.

2. Collision avoidance with other aircraft or obstacles is the responsibility of:

   1. Pilots when taxiing on the apron and in the zone not visible from TWR (see AD 2-LEVC PDC).

   2. Handling companies when towing.

3. Collision avoidance with other aircraft, equipment or people is the responsibility of:

   1. Pilots if using higher power than allowed.

   2. Handling companies during their assistance for exit manoeuvring.

4. Except for rescue and fire fighting vehicles when carrying out their specific missions, all ground movements of aircraft, towed aircraft, personnel and vehicles on the manoeuvring area are subject to prior TWR clearance.

5. All TWR clearances and instructions must be read back.

6. AREAS NOT VISIBLE FROM TOWER

PRKG C1 when PRKG C2 is occupied by another aircraft.

At the South apron, the aircraft parked near PRKG 108 screens taxiing from GATE-E to PRKG 125, 126, 127 and 151.

7. DEPARTING AIRCRAFT

   1. Pilots will request clearance to start-up engines from Valencia GMC, including the PRKG.

   2. Taxiing clearances will include the taxiing procedure up to the limit of clearance.

   3. RWY 30 runway holding position, TIRIO, has been placed in parallel to the runway instead of perpendicular, as well as the rest of runway holding positions.

8. PUSH-BACK MANOEUVRING AND TAXIING

   1. Aircraft must be ready for towed push-back or taxiing within five minutes of the approved start-up time; pilots will contact ATC if that is not the case.

   2. When aircraft is ready to push back and/or taxi, the pilot shall request advance clearance from the TWR.

   3. ATC shall only be advised of "ready to push-back" status when the manoeuvre is completely ready to start and can be accomplished within the following 30 seconds.

   4. Towed push-back manoeuvres will be carried out for all exiting aircraft at PRKG 1, 2, 3, 4, 5, 6, 6B, 22, 23, 24, 41, 42, 43 and 44.

   5. Towed push-back manoeuvres will be carried out at PRKG 25; code letter F aircraft will be nosed to the East.

   6. Taxiing along apron TWY W3 is not allowed during entry or exit operations of code letter E or F aircraft to the PRKG 25.

   7. Taxiing to the RWY 12 holding position shall be accomplished via GATE-C, unless ATC instructs otherwise.

9. ARRIVING AIRCRAFT

   1. Aircraft shall report RWY cleared and await taxiing instructions.

   2. If no taxiing instructions have been received, the aircraft, after vacating the RWY, shall stop at the end of the exit TWY segment and await instructions from TWR or a "FOLLOW ME" vehicle.

10. TAXIING RESTRICTIONS

• Use of TWY N1, M2 and S5 is available only for code letter C or lower aircraft.

• Aircraft crossing RWY 30 from TWY H1 to TWY T1 and vice versa shall report RWY cleared when the runway holding position T1 or TIRIO is overshot.

• TWY W13 is only available for access to PRKG 101 to 108.

• Taxiing via TWY N2 between GATE-C and intersection with TWY H4 will not be allowed when an aircraft is stopped at the TWY H5 holding position. Aircraft may leave via GATE-D or C, as instructed by ATC, to continue taxiing towards the apron.

• Taxiing via TWY H5 is only allowed from North to South, unless ATC instructs otherwise.

• On TWY Y1, Y2 and APN R4 the MAX aircraft allowed is code letter B.

• On TWY W1: From access to PRKG 6B to BT5, MAX aircraft allowed to taxi is code letter B.

• On TWY W5, W6, W11, W14, W15, W16, the MAX aircraft allowed is code letter C.

• On TWY W2 and CARGO RAMP the MAX aircraft allowed is code letter D.

• On TWY W3, W4, the MAX aircraft allowed is code letter E.

• On TWY W13, the MAX aircraft allowed is code letter D from GATE-E to PRKG 108. The MAX aircraft allowed from PRKG 101 to 107 is code letter C.

• To perform the turn between TWY T3 and TWY S3, aircraft may request to TWR the guidance of the "FOLLOW ME" vehicle.

• Operation of aircraft type MD-11 is not allowed in TWY H6.

11. HELICOPTER TAXIING PROCEDURE

Helicopters shall operate on RWY 12/30. In exceptional cases where technical, meteorological or emergency factors or any other circumstance are such as to advise against operating from the runway to ensure the safety of the operation, pilots may request ATC to clear operation from TWY M1 and M2.

Helicopters carrying out special urgent operations under the conditions of the letter of exemption as provided for in Article 2.3.9 of the Reglamento de la Circulación Aérea may operate from TWY M1 or M2, always under the supervision of TWR.

ARRIVALS

• RWY 12 in use

The FATO starts from the threshold of RWY 12. Helicopters shall vacate the runway preferably via TWY T2 or, if necessary, via TWY T1, T3 or T4, and will be cleared by ATC to taxi to TWY M2 or M1, via TWY SUR to use GATE-F or E to access the Apron SUR, where they will follow the indications of the "FOLLOW ME" vehicle. Either ground or air taxiing may be employed.

• RWY 30 in use

The FATO starts from the end of RWY 12 and therefore, the approach may also be accomplished from the pre-threshold area of RWY 30. Helicopters shall vacate the runway preferably via TWY T1 or, if necessary, via TWY T2, T3 or T4, and will be cleared by ATC to taxi via TWY SUR and M1 or M2, to use GATE-F or E to access the Apron SUR, where they will follow the instructions of the "FOLLOW ME" vehicle. Either ground or air taxiing may be employed.

DEPARTURES

• RWY 12 in use

Helicopters will be cleared by ATC to taxi from the stand on the Apron SUR to GATE-E, and then to taxi via TWY M1 to the intermediate holding position T1, where they will await instructions from ATC to enter RWY 12/30 and take-off on magnetic heading 120º.

• RWY 30 in use

Helicopters will be cleared by ATC to taxi from the stand on the Apron SUR to GATE-F, and then to taxi via TWY M2 and S2 to the holding position T2, where they will await instructions from ATC to enter RWY 12/30 and take-off on magnetic heading 300º.

OPERATIONAL FLIGHTS (with letter of exemption)

ARRIVALS:

• RWY 12 in use

From the North or South circuits, helicopters shall proceed on the runway heading, and parallel to the same, to the mid-point of TWY M2, subject to coordination with ATC. From there, they shall carry out ground or air taxiing to the stand, accessing the Apron SUR via GATE-F.

To facilitate correct alignment to the landing point, the following may be used as visual references the South general aviation apron (to the right in the direction of approach) and the VOR (to the left in the direction of approach).

• RWY 30 in use

From the North or South circuits, helicopters shall proceed on the runway heading, and parallel to the same, to the mid-point of TWY M1, subject to coordination with ATC. From there, they shall carry out ground or air taxiing to the stand, accessing the Apron SUR via GATE-E.

To facilitate correct alignment to the landing point, the following may be used as visual references TWY S1 (to the right in the direction of approach) and a communications antenna within the airport (to the left in the direction of approach).

DEPARTURES

• RWY 12 in use

Departure 1

From the stand, and subject to coordination with ATC, helicopters shall accomplish air or ground taxiing to TWY M1 via GATE-E. Once they have reached the approximate mid-point of the taxiway, they shall take-off on the runway heading, and parallel to the same.

To facilitate correct identification of the take-off point, the following may be used as visual references TWY S1 (to the left in the direction of take-off) and a communications antenna within the airport (to the right in the direction of take-off).

Departure 2

Helicopters requiring a take-off run shall taxi from the stand on the Apron SUR to GATE-E and, prior ATC clearance, may execute the departure procedure using the first 300 m of TWY M1, subsequently turning right to accomplish alignment with the runway heading.

To facilitate correct identification of the take- off point, the following may be used as visual references TWY S1 (to the left in the direction of take- off) and a communications antenna within the airport (to the right in the direction of take- off).

For take-off from TWY M1 with a take-off run, simultaneous operation with RWY 12/30 is not permitted.

• RWY 30 in use

From the stand, and subject to coordination with ATC, helicopters shall accomplish air or ground taxiing to TWY M2 via GATE-F. Once they have reached the approximate mid-point of the taxiway, they shall take-off on the runway heading, and parallel to the same.

To facilitate correct identification of the take-off point, the following may be used as visual references: the South general aviation apron (to the left in the direction of take-off) and the VOR (to the right in the direction of take-off).

If a take-off run is required, with RWY 30 in use, they shall taxi via GATE-F to TWY M2 and S2 up to the runway holding position T2, where they shall await instructions from ATC to enter RWY 12/30 and take-off on magnetic heading 300º.