[NDB] FW: NDB Subcommittee Meeting Postponed

Mon Apr 13 06:40:02 EDT 2020

Hello All:

Below is one more working paper for WebEx scheduled for 21 April.

I hope all are staying safe.

Sam

From: DEKER Guy <guy.deker at fr.thalesgroup.com>
Sent: Friday, April 10, 2020 12:30 PM
To: Sam Buckwalter <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 wre 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: In a Jeppesen Database, we observed that this 6th character sometime exists
  *   WG Action: Need to clarify this use (provision or actual need)

  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.
  *   WG Action: how to manage this specificity in the A424? For instance in §5.80?

  1.  Communication Records for UC/UR

  *   Thales comment: for some applications,  communication Frequency is missing for controlled and restricted airspaces (like EV records for FIR/UIR)
  *   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) in the Runway table (PG) is missing for Helipads (HA)
  *   WG action: add Ellipsoidal Height (5.225) table for such Helipads

  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 et Authorization des Procedure Data Continuation Record
     *   Qualifier 1 (valeur W)
     *   Présence FASDB associé à l'approche
  *   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 @@]

De : Sam Buckwalter [mailto:Sam.Buckwalter at sae-itc.org]
Envoyé : mercredi 1 avril 2020 20:24
À : DEKER Guy
Objet : Re: NDB Subcommittee Meeting Postponed

You can send them next week.... I will just circulate via email.

Sam

Sam Buckwalter
AMC &FSEMC Executive Secretary
Program Director

________________________________
From: DEKER Guy <guy.deker at fr.thalesgroup.com<mailto:guy.deker at fr.thalesgroup.com>>
Sent: Wednesday, April 1, 2020 2:05:24 PM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org<mailto:Sam.Buckwalter at sae-itc.org>>
Subject: RE: NDB Subcommittee Meeting Postponed

Hello Sam

We at Thales are currently closed due to the covid-19 for one week and probably more. We intended to provide the committee with working papers  but had no time to do it in due time in those circumstances.

So do you think possible to provide these subjects later, say end of next week, for discussion either for the virtual meeting or should it be for next postponed plenary?

Best regards and keep safe

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 @@]

De : ndb-bounces at mailman.sae-itc.org<mailto:ndb-bounces at mailman.sae-itc.org> [mailto:ndb-bounces at mailman.sae-itc.org] De la part de Sam Buckwalter
Envoyé : lundi 16 mars 2020 12:23
À : ndb at mailman.sae-itc.org<mailto:ndb at mailman.sae-itc.org>
Objet : [NDB] NDB Subcommittee Meeting Postponed

Hello All:

The NDB Subcommittee meeting scheduled for April 21-23 2020 in St Louis, MO is being postponed.

If you developed working papers for the April meeting please still send them to me. I will be sending out a calendar invite to virtual meeting on April 21, 2020 to discuss any items of importance that need to be address by the group.

Everyone stay safe out there.

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/>

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.

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/20200413/412cf51c/attachment-0001.html>