# SimConnect_AICreateEnrouteATCAircraft_EX1<no value>
The **SimConnect\_AICreateEnrouteATCAircraft\_EX1** function is used to create an AI controlled aircraft that is about to start - or has started - its flight plan. This function can be used with both *legacy* SimObjects, and **modular** SimObjects.

 

##### Syntax

``` cpp
HRESULT SimConnect_AICreateEnrouteATCAircraft_EX1(
    HANDLE  hSimConnect,
    const char*  szContainerTitle,
    const char* szLivery,
    const char*  szTailNumber,
    int  iFlightNumber,
    const char*  szFlightPlanPath,
    double  dFlightPlanPosition,
    BOOL  bTouchAndGo,
    SIMCONNECT_DATA_REQUEST_ID  RequestID
    );
```

 

##### Parameters

<table><thead><tr class="header"><th>Parameter</th><th>Description</th><th>Type</th></tr></thead><tbody><tr class="odd"><td><em>hSimConnect</em></td><td>Handle to a SimConnect object.</td><td>Integer</td></tr><tr class="even"><td><em>szContainerTitle</em></td><td><p>Null-terminated string containing the container title. The container title is found in the <a href="../../../../content-configuration/cfg-files/aircraft_cfg/#title">title</a> parameter of the <code>aircraft.cfg</code> file, or alternatively, you can find it from the list found in the <a href="../../../../2_DevMode/Menus/Tools/#aircraft_capture">Aircraft Capture Tool</a>. You may also retrieve the information with SimConnect using the <code>SimConnect_EnumerateSimObjectsAndLiveries</code> function.</p><p>  

Examples of aircraft titles:</p><ol><li><code>title=Boeing 747-8f Asobo</code></li><li><code>title=DA62 Asobo</code></li><li><code>title=VL3 Asobo</code></li></ol></td><td>String</td></tr><tr class="odd"><td><em>szLivery</em></td><td><p>Null-terminated string containing the livery name. This field is only required when checking <strong>modular</strong> SimObjects, since their liveries are dynamically handled and do not have a unique <a href="../../../../content-configuration/cfg-files/aircraft_cfg/#title">title</a> parameter like legacy aircraft.</p><p>This parameter can be set to either the <em>name</em> of the livery as defined in the <code>name</code> parameter of the <code>livery.cfg</code>, or to the <em>folder name</em> of the livery in the package. Note that you can also get the livery name using the <code>SimConnect_EnumerateSimObjectsAndLiveries</code> function.</p><p>The function will check for the <strong>folder</strong> first, then the <strong>parameter name</strong> second, and if the given name is not found in either location, then the default livery will be used.</p></td><td>String</td></tr><tr class="even"><td><em>szTailNumber</em></td><td>Null-terminated string containing the tail number. This should have a maximum of 12 characters.</td><td>String</td></tr><tr class="odd"><td><em>iFlightNumber</em></td><td>Integer containing the flight number. There is no specific maximum length of this number. Any negative number indicates that there is no flight number.  

<em>szFlightPlanPath</em>.</td><td>Integer</td></tr><tr class="even"><td><em>szFlightPlanPath</em></td><td>Null-terminated string containing the path to the flight plan file. Flight plans have the extension .pln, but no need to enter an extension here. The easiest way to create flight plans is to create them from within Microsoft Flight Simulator 2024 itself, and then save them off for use with the AI controlled aircraft.</td><td>String</td></tr><tr class="odd"><td><em>dFlightPlanPosition</em></td><td>Double floating point number containing the flight plan position. The number before the point contains the waypoint index, and the number afterwards how far along the route to the next waypoint the aircraft is to be positioned. The first waypoint index is 0. For example, 0.0 indicates that the aircraft has not started on the flight plan, 2.5 would indicate the aircraft is to be initialized halfway between the third and fourth waypoints (which would have indexes 2 and 3). The waypoints are those recorded in the flight plan, which may just be two airports, and do not include any taxiway points on the ground. Also there is a threshold that will ignore requests to have an aircraft taxiing or taking off, or landing. So set the value after the point to ensure the aircraft will be in level flight.</td><td>Float</td></tr><tr class="even"><td><em>bTouchAndGo</em></td><td>Set to True to indicate that landings should be touch and go, and not full stop landings.</td><td>Bool</td></tr><tr class="odd"><td><em>RequestID</em></td><td>Specifies the client defined request ID.</td><td>Integer</td></tr></tbody></table>

 

##### Return Values

The function returns an **HRESULT**. Possible values include, but are not limited to, those in the following table.

{{< table-wrapper >}}

| Return value | Description             |
|--------------|-------------------------|
| S\_OK        | The function succeeded. |
| E\_FAIL      | The function failed.    |

{{< /table-wrapper >}}


 

##### Remarks

An enroute aircraft can be on the ground or airborne when it is created by this function. Typically this will be an aircraft flying under IFR rules, and in constant radio contact with ATC. The following exceptions can be created by this function (refer to the [SIMCONNECT\_EXCEPTION](../structures-and-enumerations/simconnect-exception/) enum for more details):

-   `SIMCONNECT_EXCEPTION_LOAD_FLIGHTPLAN_FAILED`
-   `SIMCONNECT_EXCEPTION_CREATE_OBJECT_FAILED`

 

A [SIMCONNECT\_RECV\_ID\_EVENT\_OBJECT\_ADDREMOVE](../structures-and-enumerations/simconnect-recv-id/) event notification can be subscribed to (see the [SimConnect\_SubscribeToSystemEvent](../general/simconnect-subscribetosystemevent/) function), which will return a [SIMCONNECT\_RECV\_EVENT\_OBJECT\_ADDREMOVE](../structures-and-enumerations/simconnect-recv-event-object-addremove/) structure whenever any client, including the one making the change, successfully adds or removes an AI controlled object.

 

For float-planes the recommended procedure is to control them using waypoints, and not the ATC system, as there is no concept of a "parking space" after a water landing. So, the waypoints of the route of the float-plane should include the route that it should follow before take off and after landing. For all these cases of controlling aircraft using the client, or using waypoints, set up the object using the [SimConnect\_AICreateNonATCAircraft\_EX1](simconnect-aicreatenonatcaircraft-ex1/) call.