-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A-CDM & Flow Management System #19
Comments
Chat history on 10/10: Discord (internal) |
TOBT拟定三种方式:
注意:
|
TSAT的时间:
最终TSAT取上述最大值,TSAT窗口期改为-5 +10 注意:如果有slot,那slot=CTOT=TTOT,通过滑行时间反推TSAT,没有slot再按上述规则计算。 |
FMP可以给出的限制:
|
Design Doc# A-CDM Design Doc
Participants
Flight PhasesScheduledAll flights with (1) a submitted flight plan, (2) is within 20nm of the planned departure airport and (3) is within 250ft AGL of the planned departure airport, should be put in this phase upon discovery. The pilot is expected to (1) do their flight preparations, (2) submit a TOBT (Target off-block time) as soon as possible on A-CDM website and (3) request for clearance delivery after submitting a TOBT.
The controller is expected to (1) acknowledge the scheduled flight and do relevant preparations and (2) respond to clearance request and assign a valid physical runway to the flight.
The A-CDM system is expected to (1) track the flight, the flight plan and the submitted TOBT for further usage and (2) calculate the departure gate from realtime network data.
Pre-departureThe flight are moved from Scheduled to this phase as (1) the pilot requests for clearance delivery (2) the controller assigns a valid runway to the flight. The pilot is expected to (1) complete their ground services based on the COBT (Calculated off-block time) published (2) request for pushback and start-up clearance within the TSAT (Target start approval time) window (TSAT -10/+5 min).
The controller is expected to (1) confirm the TTOT (Target take-off time) computed by A-CDM system to become CTOT (Calculated take-off time) and (2) issue pushback and start-up clearance within the TSAT window.
The A-CDM system is expected to calculate the ETOT, CTOT and TSAT as soon as the flight moves to the current phase within 15 seconds.
The A-CDM system is expected to record the ASAT (Actual start approval time) based on the telemetry from the radar client.
Departure TaxiThe flights are moved from Pre-departure to this phase as the pilot receives the pushback and start-up approval.
The pilot is expected to taxi from the gate to the runway threshould / holding point targeting at the CTOT. The controller is expected to give a take-off clearance based on the CTOT window (CTOT -/+ 5 min). The A-CDM system is expected to record the ATOT (Actual take-off time) based on realtime network data or the telemetry from the radar client.
CruiseThe flights are moved from Departure Taxi to this phase as the flight is airborne.
The pilot is expected to check the latest assigned gate. The controller is expected to check the latest assigned gate. The A-CDM system is expected to (1) calculate and update the ETO (Estimated time of overfly) and ELDT (Estimated landing time) based on real-time network data (2) record the ALDT (Actual landing time) based on realtime network data or the telemetry from the radar client (3) calculate and update the target gate based on realtime network data and (4) calculate the landing runway based on realtime network data.
Arrival TaxiThe flights are moved from Cruise to this phase as the flight is landed.
The A-CDM system is responsible for (1) calculating the EXIT (Estimated taxi-in time) based on the airport, runway and gate (2) calcuate EIBT (Estimated in-block time) based on ALDT + EXIT and (3) record the relevant times.
FinalizationThe flights are moved from Arrival Taxi to this phase as the pilot reports in-block.
References修改建议 from Rudi
TSAT优先级:
|
与A-CDM系统联动的流控系统,访问权限可以和ATC Center同步,有TMU权限的人可以访问
The text was updated successfully, but these errors were encountered: