===== Why doesn’t my TPFDD-delivered squadron fly? =====

The squadron’s authorization quantity may not be met by the delivery.  If the air assets are designated as critical [pacing] items, a squadron it won’t activate unless it has reached a certain percentage of the authorized quantity.  BSE(BSE Type) Data >> BSE(Type)ActivationSpecifications gives the % of authorized Air_Assets required to activate the Air Unit BSE.

This table may help with understanding how TPFDD deliveries affect Air Units in JAS:


^CASE   ^SITUATION                                             ^IMPLEMENTATION^
|Case 1	|All aircraft in place at time 0 initialization	       |Assign resources to squadron BSE or BSE type|
|Case 2	|Squadron only gets aircraft at later time via TPFDD   |Assigning a TPFDD RLN to the squadron will prevent it from activating at initialization, but will activate it upon delivery of the RLN|
|Case 3	|Squadron has initial aircraft, and receives additional later via TPFDD	|As described above, simply having an RLN assigned for a squadron will prevent it from activating prior to the RLN delivery.  To allow the initial plus subsequent delivery of aircraft to work requires 2 RLNs:  1. Initial RLN "In Place" (i.e. time 0) for initial quantity of aircraft; 2. Subsequent RLN for TPFDD delivery at a later time.|


If the KB Facts shows initiating event (ex. D-Day) at the proper time, but TPFDD doesn’t kick off, try this:  In KB, [US]JTF, Transition Facts, for the appropriate Phase or State, put in a new Action in the lower right pane:  Execute An Order >> Issue An Order To TRANSCOM for the appropriate FDO at time Immediate.  This will show in KB Actions, and will tell TRANSCOM when to start incrementing days from the Initiating Event.