500
Name one of the 11 possible reasons an aircraft did not receive his PDC.
What is
a. Only one PDC per 24-hour period (per tail-number/flight ID) per departure airport can ever be issued. Note: This means that even if the requests are on different calendar days, only one in a 24-hour period will be honored.
b. The aircraft requested the clearance before the controller has had a chance to issue it. If they will wait until 25 minutes before their P-Time before they actually request the PDC from their datalink provider, they will generally get it (unless the clearance delivery fellow is super busy or there is another reason - see the rest of this list). This assumes the flight plan was filed sufficiently in advance.
c. There is a revision to the flight plan (doesn't matter if it was user requested, traffic management requested, SWAP in effect, etc.), if there is a revision, there is no PDC, end of story. Not just route revisions can cause this, even an ETD change counts.
d. There is a problem with the route/plan as filed (wrong way down a one way airway, airway is closed, etc.) and the computer or the traffic management unit kicked it out requiring a "full route clearance".
e. The tower download did not take place as scheduled, so a new PDC customer was not added for that tower when expected. This refers to the list of tails the datalink provider sends twice a month. Each tower must download and install the new list individually.
f. The tower download did not take place as scheduled, so an existing PDC customer was not changed over to his/her new datalink provider, so the tower routes the PDC to the old provider. This refers to the list of tails the datalink provider sends twice a month. Each tower must download and install the new list individually.
g. The tower granted the PDC, but the datalink provider rejected it as non participating. We at ARINC Direct accept ANY PDC that is sent to us, so this reason does not apply to us.
h. The tower granted the PDC, but the network between the tower and the datalink provider was down, so the request to send it to the provider timed out. If this was the case, we'd have many other problems. The possibility of this is extremely low, and we'd all know if it was the cause.
i. The tower granted the PDC, but the datalink provider did not receive it. Again, this would be very rare, happening only if our systems here in ARINC Direct were down.
j. The tower controller made a mistake and "dumped" the request. (this one happens about once a month per tower).
k. The tower re-routed flight strip traffic to a non-PDC printer, and therefore PDC didn't see it (this one almost never happens).