Title: DFIS - "Water on runway" Indication in D-ATIS Report PDR Reference: M1080001 Originator Reference: SARPs Document Reference: DFIS, Section 2.4.4.3 CAMAL Document Reference: DFIS, Section 5.6.3.3 P/OICS Document Reference DFIS, P-9 "runway" sheet Status: ADOPTED Impact: A (FIS) PDR Revision Date: 30/01/02 (RESOLVED -> ADOPTED) 24/09/01 (ACCEPTED -> RESOLVED) 05/09/01 (SUBMITTED -> ACCEPTED) 24/08/01 (SUBMITTED) Submitting State/Organization: ATNP/WGA-SGA2 Submitting Author Name: Picard, F Submitting Author E-mail Address: picard_frederic@stna.dgac.fr Submitting Author Supplemental Contact Information: tel. +33.5.62.14.55.33 fax. +33.5.62.14.54.01 SARPs Date: Doc 9705 Ed 2 Doc 9705 Draft Ed 3 (ICAO web site - 11/00) CAMAL Date: Doc 9739, Prop. Ed 2 (ATNP web site, 06/01) P/OICS Date: Version 2.0, June 2001, SARPs Language: English Summary of Defect: The OPLINK WP/B decided at its March 2001 meeting (Redondo Beach) to include a new optional field in the runway surface conditions component of the D-ATIS reports. From OPLINKP/WG/B-WP/125 "Summary of Discussions and Conclusions": "The working group was made aware that during a Secretariat review of the D-ATIS template contained in the summary of discussions of the Berlin meeting, the Aerodromes, Air routes and Grounds Aids (AGA) section identified a missing element concerning the runway surface conditions. Annex 14 - Aerodromes, Volume I - Aerodrome Design and Operations, paragraph 2.9.5 states "information that a runway or portion thereof may be slippery when wet shall be made available". The working group agreed to include a new optional element RWY SLIPPERY after the "Mean depth (O)" element within the significant runway surface conditions field [field 3(a)] as follows: ------------------------------------------------------------------------------ | Field 3(a) | Means depth (O) | [CLEAR AND DRY.... | ------------------------------------------------------------------------------ | | Water on runway | RWY SLIPPERY | | | (O) | | ------------------------------------------------------------------------------ | | Friction | ... | | | Measurements | | ------------------------------------------------------------------------------ Assigned SME: Sub-Volume II SME P/OICS SME Proposed SARPs amendment: 1/ Version 1 DFIS - Change the ASN.1 definition of ConditionsAndActions in section 2.4.4.2.1 from: ConditionsAndActions ::= SEQUENCE { timeOfObservation [0] Time OPTIONAL, runwayId [1] RunwayId OPTIONAL, length [2] RunwayLength OPTIONAL, width [3] RunwayWidth OPTIONAL, deposits [4] RunwayDeposits OPTIONAL, frictionMeasurements [5] FrictionMeasurements OPTIONAL, ... } to: ConditionsAndActions ::= SEQUENCE { timeOfObservation [0] Time OPTIONAL, runwayId [1] RunwayId OPTIONAL, length [2] RunwayLength OPTIONAL, width [3] RunwayWidth OPTIONAL, deposits [4] RunwayDeposits OPTIONAL, frictionMeasurements [5] FrictionMeasurements OPTIONAL, ..., runwaySlipperyIndication [6] BOOLEAN OPTIONAL } 2/ Version 2 DFIS - Change the ASN.1 definition of ConditionsAndActions in section 2.4.4.3.1 from: ConditionsAndActions ::= SEQUENCE { timeOfObservation [0] Time OPTIONAL, runwayId [1] RunwayId OPTIONAL, length [2] RunwayLength OPTIONAL, width [3] RunwayWidth OPTIONAL, deposits [4] RunwayDeposits OPTIONAL, frictionMeasurements [5] FrictionMeasurements OPTIONAL, ... } to: ConditionsAndActions ::= SEQUENCE { timeOfObservation [0] Time OPTIONAL, runwayId [1] RunwayId OPTIONAL, length [2] RunwayLength OPTIONAL, width [3] RunwayWidth OPTIONAL, deposits [4] RunwayDeposits OPTIONAL, frictionMeasurements [5] FrictionMeasurements OPTIONAL, ..., runwaySlipperyIndication [6] BOOLEAN OPTIONAL } Proposed CAMAL amendment: 1/ In Table III-5-x Runway Surface Conditions, add the new table raw as follows: ------------------------------------------------------------------------------ | | Water on runway | RWY SLIPPERY | | | (O) | | ------------------------------------------------------------------------------ and change the ASN.1 definition as specified above. 2/ Replace the note of section 5.4.3.6.3 from: "Note. - The extensibility feature is not used for D-ATIS since the version 1 and version 2 ASN.1 description for D-ATIS messages are fully aligned. The feature will be used in future versions to guaranty interoperability with FIS version 2, when ATIS or METAR fields will have to be added in the FIS reports. More information on the ASN.1 extensibility feature can be found in [Ref. 6]." To: "Note. - More information on the ASN.1 extensibility feature can be found in [Ref. 6]." 3/ Add a new section 5.4.3.6.4 as follows: 5.4.3.6.4 The extensibility feature is already used for handling the new D-ATIS report component RUNWAY SLIPPERY INDICATION. Version 1 or 2 implementations can choose to support this new ASN.1 field without jeopardizing the technical interoperability. Implementations with or without the new field will always be able to interoperate. An implementation not supporting the new field but which would receive it would ignore the field, and act as if not received. Proposed P/OICS amendment: 1/ Airborne P/OICS: In P-3 "Protocol-Id", add this PDR reference (M1080001) in I-3.4 2/ Airborne P/OICS: In P-9 "Runway" sheet, add a new line as follows Ref No: P-9.9,08 Operational Elements: ... a "runway slippery" indication Send OPLINKP Profile: - Profile Status: blank Profile Cons: blank Impl. Status: blank Impl. Cons blank Receive OPLINKP Profile: O Profile Status: blank Profile Cons: blank Impl. Status: blank Impl. Cons blank ASN.1 Protocol Elements: [6] BOOLEAN OPTIONAL Note blank 3/ Airborne P/OICS: In P-3 "Protocol-Id", add this PDR reference (M1080001) in I-3.4 4/ Ground P/OICS: In P-9 "Runway" sheet, add a new line as follows Ref No: P-9.9,08 Operational Elements: ... a "runway slippery" indication Send OPLINKP Profile: O Profile Status: blank Profile Cons: blank Impl. Status: blank Impl. Cons blank Receive OPLINKP Profile: - Profile Status: blank Profile Cons: blank Impl. Status: blank Impl. Cons blank ASN.1 Protocol Elements: [6] BOOLEAN OPTIONAL Note: blank Impact on interoperability: There is no impact on *technical* interoperability since the new field is added after the extensibility marker. Implementations with or without the new field will be able to interoperate. An implementation not supporting this PDR resolution which would receive the RWY SLIPPERY indication would ignore the field, and act as if not received. There is no safety issue. The RWY SLIPPERY indication shall be sent when available on the ground, whatever are the air and ground version number. When either the air or the ground is version 1, the indication can be sent as a free text message in the specificATISInstruction. PDR Validation Status: ASN.1 compilation using an independant tool. SME Recommendation to CCB: RESOLVED CCB Decision: atnp_ccb_chair (24/08/01): SUBMITTED atnp_ccb_chair (05/09/01): ACCEPTED CCB-14 (Toulouse): no meeting atnp_ccb_chair (24/09/01): RESOLVED