Equipement Requirements

Hi all,

Can you please implement a feature that looks for the specific requirements for certain routes and/or airspaces before suggesting routes that are within the airspace or follow certain airways? For example I am now flying an aircraft without HF radio and it suggested a route that requires it (T9 airway).

I would be very happy if this would be possible!

Kind regards,

Problem is who would maintain that, for airspace updates occur every 56 days USUALLY. While the requirements are sort of simple, but it depends on the type of operation which you are conducting (in the RW anyway); US 121, 135, 91 GA, etc all have differing comms requirements for example for ops in the ocean. Those equipment requirements are buried, and I mean buried, usually somewhere deep in the host nation AIP, or the regs for the operator. Some are airway specific, some are FIR specific.

At work we are starting later this year on deploying a new flight planning system - a multiyear project on which I’ll get to participate; when I was in Europe this past fall I met some of their staff at their HQ; they have a whole workgroup (maybe 10-15 people a shift) who works 24/7 to monitor the AIPs of the world and if lets say Turkey were to now require Inmarsat SATCOM ground to unlimited by a change in the AIP ENR, they’ll make the changes in their system to deploy it so when that requirement were to go live, and if an FPL doesnt have that alphabet soup in the filing, it’ll kick it back; and this was a whole department - not an Army of one doing this as a part time gig. They’ll be looking for the page change bars in every AIP, and they are all licensed dispatchers. They’ll also monitor the worldwide NOTAM feed so if a segment of an airway is closed, say a portion of the L888 airway in China - they close it so it doesnt get used.

I like the idea, but I dont see this as something that would be easily accomplished.

1 Like