1 / 12

D-TAXI & D-RVR updates

D-TAXI & D-RVR updates. Christian Bousmanne 78/214 Maastricht, June10, 2009. List of main issues. Scope of the service Content of the message Filtering rules Issues in Contract mode About validation and testing. Scope of the service. The D-RVR service can be used

claude
Download Presentation

D-TAXI & D-RVR updates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D-TAXI & D-RVR updates Christian Bousmanne 78/214 Maastricht, June10, 2009

  2. List of main issues • Scope of the service • Content of the message • Filtering rules • Issues in Contract mode • About validation and testing.

  3. Scope of the service • The D-RVR service can be used • before take off so as to obtain departure runway parameters in timely manner • after take off as the departure airport is very frequently the preferred “departure alternate”. • (En route, in case of diversion airport monitoring) • Before arrival. • What about downlink of RVR requirements for individual A/C?

  4. Content of the message • Time. • + for each selected airport • Airport ID (ICAO)+ for each selected runway • Runway identifier, e.g., 26L. • RVR value at the runway touchdown point. • RVR value at the runway midpoint. • RVR value at the runwayrollout point • RVR trend at the runway touchdown point,. • RVR trend at the runway midpoint, • RVR trend at the runway rollout point, • The visibility threshold as indicated in the request, if any • Status of the runway edge lights • Status of the runway centerline lights.

  5. Filtering « what » rules ! • Visibility threshold parameters: (list non exhaustive so far) • TDZ, MID, END RVR = XXX meters • Any selection or combination of following • TDZ RVR = XXX meters • MID RVR = YYY meters • END RVR = ZZZ meters • => what are associated rules of presentation to the flight deck. 2 scenario to consider.

  6. Filtering “when” rules • Uplink responses shall be sent every time at least one of the relevant RVR value has changed (which is more frequent than ATIS). • However they will only be presented to flight crew on regular time interval, as selected in the request (update rate parameter) (e.g. : every minute); except when the visibility threshold as set by the flight crew is reached. (see following slides) • In Contract mode, if no RVR has changed during the elapsed time within the update time span, then the ground system shall transmit a specific message ‘e.g.: no RVR change”)

  7. Scenario 1 : increasing visibility • The RVR parameters are provided to the crew as soon as one of the selected runway threshold is reached.. • All available RVR parameters associated to that specific runway are also presented, even if below their specific threshold. • The RVR parameters of those other selected runways that have a minimum of one value above related threshold are provided to the crew in the same message.

  8. Scenario 2 : decreasing visibility • The RVR parameters are provided to the crew as long as one of the selected threshold for a specific runway is lower than the actual value.. Other parameters are also presented, even if below the threshold • The RVR parameters of those other selected runways that have a minimum of one value above their related threshold are provided to the crew in the same message. • When all the RVR parameters for a specific runway fall below the threshold, a specific message is send/displayed to the flight crew.

  9. Issues in Contract mode • Do we allow several contracts to be placed in parallel for several airports? (text and or display?? ) • Termination criteria The “Update Contract” shall be terminated upon: • Manual transmission of a D-RVR Termination (RTT) message by the ground system; • Manual contract cancellation by the flight crew.(RTT) • Automatic termination of the contract possible • on final approach, or • on landing detection, • or on triggering of a specific criterion as indicated by the flight crew. Questions : what are your proposals ?

  10. About validation and testing • Real time simulation? : • How close do we want to get to real situation? • Which elements in particular do we want/need to assess? • HMI “design” : graphic/text only? • Flight operations • Need for : Airport / airline / ground system / data link provider • Risk associated to the probability of occurrence ??

  11. Validation Aircraft? full flight sim? OBJECTIVES EHAM 0824 RWY 01 L TDZ 325 MID 250 END 300 ATC TOWER SERVER EFB? / MCDU? / ND RVR meter airport system

  12. Thank you Christian.bousmanne@eurocontrol.int

More Related