mSparks43 / XPlane-11-AutoATC-plugin

C/C++ Source code for Xplane AutoATC plugin
GNU Lesser General Public License v3.0
16 stars 7 forks source link

Ticketing/User aircraft tracking #80

Open JT8D-17 opened 4 years ago

JT8D-17 commented 4 years ago

ATC should actively monitor the state of the user aircraft and issue calls.

My personal take on the matter:

IFR Clearance: Ticket with an expiry time (needs re-clearing when expired), expiry timer runs from requesting clearance to being airborne, ticket valid until handoff to approach (or landing). Can be cancelled at any point to revert to VFR with flight information (if applicable) or a new IFR clearance. Needs to be requested at any point prior to takeoff. May also be applied to VFR flight plans.

Altitude: An altitude ticket applies in uncontrolled VFR for airspace type (warning if vertically outside of VFR approved airspace) and for VFR and IFR flight plans. ATC monitors user aircraft altitude and issues clearances based on traffic situation, terrain and SID/STAR restrictions. Warns user aircraft when filed altitude deviates by +/- 500 ft. User may request a different altitude though (for situational climbs/descends).

Ground operations: Applied when requesting taxi, either for departure or after landing. ATC monitors user aircraft and issues holds based on traffic situation (AI aircraft, crossing runways). User may request taxi to parking or taxi for takeoff. Will be cleared when at hold short point, flight completion (arrival at parking spot) or manually by user.

Departure: Departure clearance tickets are issued by requesting departure when at hold short. Involves SID information or vectors to a departure point and altitude clearances based on traffic situation and/or SID waypoint altitude restrictions. An aborted departure will close this ticket and revert to a ground ops ticket or an arrival/landing ticket. ATC should monitor speed to keep user below 250 KIAS below 10000 ft. Ticket will be cleared at end of SID or with ARTCC handover or upon a predetermined waypoint. After that, user may resume own navigation.

En route: En route tickets apply to a user aircraft that does neither have a departure nor an arrival ticket, but is airborne upon checking in with ARTCC (or a departure/arrival agency). Checks agency boundaries and issues handover calls. In uncontrolled VFR, traffic and restricted/unavailable airspace avoidance instructions should be issued. VFR with flight plan should be monitored for weather, issuing warnings if the meterological conditions do not permit continuing flight under VFR. IFR flights should be monitored for altitude compliance and traffic avoidance.

Weather deviation: Subticket to apply to the en route ticket when user requests a temporary deviation from the filed flight plan for weather. Will offer a waypoint at which user has to be back on the original flight plan (may be negotiable).

Alternate deviation: Cancels current flight plan ticket and issues a suitable clearance (ruleset inherited from original clearance) for the alternate.

Arrival: When flying a filed flight plan en route agency will issue descent instructions based on a 3° flight path and the altitude constraint of the first STAR waypoint OR altitude of the downwind or base leg (depending on user heading relative to landing runway) of the arrival runway (when no STAR is available or desired). Ticket will inherit flight ruleset (VFR/IFR) and clearance. Will clear for a STAR one is set or desired by the user, monitoring compliance with altitude and speed restrictions on the way. Will vector user aircraft when no STAR is available or user requests so, monitoring speed and altitude. ARTCC will hand over to the arrival agency at a suitable distance or time from the destination. Ticket is completed with transition to arrival tower.

Landing: Ticket is opened when user aircraft is handed off to the tower. Monitors airport traffic situation and user aircraft glide path, may instruct a go-around when runway is blocked or user aircraft is in a visibly unstable or unsafe approach condition. A go around will close this ticket and issue a new arrival ticket with the arrival agency. Ticket is closed when user aircraft announces that the runway is vacated.

Emergency: An emergency ticket depends on the agency it is issued with. Departure agencies will issue a priority landing ticket, providing a vector to the entry point for a final approach). En route agencies will provide vectors to the nearest suitable airport/airfield and a priority ticket at the arrival agency that will cut short a standard approach and provide vectoring to the final approach entry point. Arrival agencies will provide a priority landing ticket with vectors to a final approach entry point.

mSparks43 commented 4 years ago

some videos on this issue:

https://youtu.be/GVOeteqUiOw

https://youtu.be/LK3TFVIlhYw

https://youtu.be/HCqKLmTAHZg

https://youtu.be/sGADIXhJje8

mSparks43 commented 3 years ago

Two key ones to start with are QNH and runway - i.e. what has the pilot been given, just about to start testing these now. others include procedures such as SID and STAR. Basically anything that could change is right in the hot seat. Any kind of clearance issued and the information associated with it needs to be remembered for a period of time, because as circumstances change if it becomes invalid it needs to be handled accordingly.