[NDB] FW: NDB Subcommittee Meeting Postponed

Thu May 28 06:00:17 EDT 2020

All:

Please see the updated list from Thales.

Sam Buckwalter
Program Director
Executive Secretary AMC
o +1.240.334.2576
c  +1.443.454.0584
 sam.buckwalter at sae-itc.org<mailto:sam.buckwalter at sae-itc.org>
www.aviation-ia.com<http://www.aviation-ia.com/>

From: DEKER Guy <guy.deker at fr.thalesgroup.com>
Sent: Thursday, May 28, 2020 5:54 AM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org>
Subject: RE: NDB Subcommittee Meeting Postponed

Hi Sam,

I would like to update our question list (see below)

Best Regards

Guy

From: DEKER Guy <guy.deker at fr.thalesgroup.com<mailto:guy.deker at fr.thalesgroup.com>>
Sent: Friday, April 10, 2020 12:30 PM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org<mailto:Sam.Buckwalter at sae-itc.org>>
Subject: RE: NDB Subcommittee Meeting Postponed

Dear Sam,

As mentioned in my last mail, below is a list of subjects of interest for us that were reported to me and that could be addressed at the next or a further meeting either virtual or plenary.
Sorry for being late (after Working papers were posted last Wednesday) and for not using the working paper template as the current re-organization we have due to covid-19 affects my availability for current standards including this committee.

  1.  4.1.24.1 Preferred Route Primary Records.

  *   Note 1: The Standard Enroute Airway Identifier is five characters. Some users envision the need for a sixth character. This field length will permit such coding; see Section 5.8.
  *   Thales comment:  Preferred Route Ident is 10 characters  and this note address Enroute Airway (which is 5 characters long). This note is unconsistent and should be removed.
  *   WG Action : remove note 1 for 4.1.24.1

     1 Bis)  4.1.6.1/4.1.21.1/4.1.21A.1/4.1.21B.1/4.1.21C.1  Enroute Airways & restrictions Primary Records.

  *   All Enroute Airways & Restriction records (4.1.6.1,  4.1.21.1, 4.1.21A.1, 4.1.21B.1, 4.1.21C.1) have a note 1 allowing for a 6th character In a Jeppesen Database,
  *   Thales comment: Indeed, we observed that Airway Ident with 6th character sometime  exists. However, actual length (see 5.8 definition) is still 5 characters. Last Seattle meeting expressed a need for change (in XML only) but only for Terminal procedures, not for airways.
  *   WG Action: Need to clarify Airway Ident length is still 5.

  1.  5.7 Route Type (RT TYPE) Table 5-6 - Airport and Heliport SID Record

  *   Note 4: The Qualifier F indicates that the departure is an RNP AR procedure. Implied GNSS required. Qualifier F used with SID route type 0 will designate an RNP AR Engine Out SID. Qualifier F can be used in conjunction with SID route type 1, 2 or 3, provided the corresponding SID transition is AR.
  *   Thales comment : Today the qualifier F is used for the whole procedure. But the note suggest that when there is an AR Engine out SID (type 0), we can have also other SID transition (type 1, 2 or 3)  in conjunction with the EO SID.
  *   WG Action: Clarify use of qualifier F for all SID Route type or only for AR EO SID

  1.  5.80 ILS/MLS/GLS Category (CAT)

  *   Thales comment : In the light of two AIP charts concerning the ILS/LOC and ILS SA CAT I (Special Authorization) procedures for runway RW04L at KEWR (Newark), there is only one coded procedure "I04L" in the A424 source file, meaning the two procedures are identical from an A424 point of view. Do we confirm there is no specific A424 coding of A424 value for ILS SA CAT I approach procedure? A crew would appreciate to make the distinction in order to proceed to the specific  minima for SA CAT I, so, it seems that this information is missing and should be worth be indicated in a 424 record.
  *   Although this subject was included in the Attachment 8 from GARMIN, this was only for XML.
  *   WG Action: how to manage this specific need in the A424 ASCII file? For instance in §5.80 below (not sure)?
[cid:image003.jpg at 01D634E6.ADD024B0]

  1.  Communication Records for UC/UR

  *   Thales comment: for some applications,  communication Frequency (7 characters) is missing for controlled and restricted airspaces (like EV records for FIR/UIR).
  *   Thales proposal: to add For controlled airspace, this 7 characters field could be for instance be within blank space 45 to 123 of UC Controlled Airspace Primary Extension record (4.1.25.3).
However For Restricted Airspace,  no room available within UR Restricted Airspace Primary Record (4.1.18.2), as there is no extension record.

  *   WG action: add a record for communication frequency associated to controlled or restricted airspaces.

  1.  SBAS provider

  *   Thales comment: SBAS provider information is useful in order to manage LNAV/VNAV SBAS approaches
  *   WG action: add SBAS provider field in an A424 record

  1.  4.1.36.1 Airport Helipad Primary Records  and 4.2.9.1 Heliport Helipad Primary Records

  *   Thales comment: In order to define virtual FASDB for Helipad, the equivalent of Ellipsoïd Height (5.225, 6 characters) as in the Runway table (PG) is missing for Helipads (HA, PH, HH)
  *   Possible proposal:
     *   For Heliport Records (HA):

-> Column 86 to 91 Heliport Primary Records (4.2.1.1)( 86 to 91 currently reserved for expansion)

     *   For Airport Helipad Record (PH):

-> column 105 to 110 of Airport Helipad Primary Records (4.1.36.1) (105 to 123 are reserved for expansion)

     *   For Heliport Helipad Record (HH):

-> column 105 to 110 of Heliport Helipad Primary Records (4.2.9.1) (105 to 123 which are reserved for expansion)

  *   WG action: add Ellipsoidal Height (5.225) for such Helipads records

  1.  Level of service

  *   Thales comment: There seems to be inconsistencies between navigation databases from various providers  concerning the following labels in the ARINC 424:
     *   GNSS/FMS Indicator
     *   Level of Service and Authorization of Procedure Data Continuation Record
     *   Qualifier 1 (value W)
     *   FASDB associated to the approach
  *   WG action: explain how to interpret those labels (appendix or comment)

Best regards

Guy DEKER
Flight Management System Expert Senior
Extended FMS IPC & Standards
*: +33 5 61 19 75 01 / Cell : +33 6 76 80 40 55
* guy.deker at fr.thalesgroup.com<mailto:guy.deker at fr.thalesgroup.com>
THALES AVS France SAS
Flight Avionics
105 Avenue du General Eisenhower 31036 TOULOUSE, FRANCE
[@@ THALES GROUP @@]

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. This email, and any attachments, may contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and permanently delete any printout of the message, the original and any copy of the e-mail and its attachments from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/ndb/attachments/20200528/42b5e7c4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 27534 bytes
Desc: image003.jpg
URL: <http://mailman.sae-itc.org/pipermail/ndb/attachments/20200528/42b5e7c4/attachment-0001.jpg>