The Tech Log product suite has an integration with the flight planning tool RocketRoute. Customers of both TrustFlight and RocketRoute can take advantage of this integration to have filed flight plans automatically appear within the TrustFlight system, reducing the amount of data that flight crew need to manually enter.

Functionality

The integration operates automatically in the background to import filed flight plans as "Draft" sectors against your aircraft, in addition to importing all flight crew members from RocketRoute into your Tech Log organisation. This article focuses on the parts specific to the RocketRoute integration. You can find out more about working with draft sectors in this article: Explanation of a Draft Trip.

Synchronisation 

The integration automatically synchronises 3 sets of information from RocketRoute to the Tech Log Core server:

• Aircraft are synchronised every 4 hours. Adding a new aircraft to your RocketRoute account may take up to 4 hours before flight plans will start synchronising to Tech Log.
• Flight crew are also synchronised every 4 hours. Adding a new crew member to your RocketRoute account will take up to 4 hours before they appear in the Tech log application suite.
• Flight plans are synchronised every 10 minutes in order to reduce the amount of time before filed or altered flight plans are updated within our system. At busy times it can take slightly longer for changes to be reflected within the Tech Log application suite, however.

Flight Import Logic

Flight plans are only imported once they are filed within RocketRoute. At this point, the plan and any subsequent updates to it are automatically brought into Tech Log. As RocketRoute does not group flights into Trips, this happens automatically as flights are imported. It is important to note that if flight plans are altered, their suitability to be included in the same trip will be reevaluated, and as such, draft trips may be automatically created and removed in line with updates in RocketRoute.

All trips within Tech Log must fall on the same date (in UTC) and have the same crew. For the purposes of grouping trips from RocketRoute, however, we apply slightly different logic for single and multicrew aircraft. For aircraft approved to fly with a single pilot, the PIC on the filed flight plan must match the PIC on the Tech Log trip record. For multicrew aircraft, the PIC simply must exist on the trip as either the PIC or SIC, catering for the ability to change the crew acting as PF on any sector of a trip.

Multiple draft trips can exist against the same aircraft as a consequence and depending on how far in advance flight plans are filed in RocketRoute. Only the next trip will be shown on the iPad application's dashboard, but the draft trips can be viewed in full on the Trip Logs page.

Some important considerations when working with draft trips:

• Sectors that are marked as active within Tech Log will not be automatically deleted should the flight plan be abandoned in RocketRoute. These will need to be manually abandoned or deleted within Tech Log.
• Flight plans that fall before a sector that has already been started in Tech Log will not be automatically imported from RocketRoute. Only sectors after the "in progress" sector will be imported.
• If a sector is simultaneously created in Tech Log and RocketRoute, the Tech Log application will attempt to identify this occurrence and merge the two records together to prevent duplicate sectors appearing in the system. For this to happen, the sectors must fall against the same trip (i.e. same date and crew), and the recorded takeoff time must fall within 1 hour of the planned departure time on the filed flight plans.

 Troubleshooting

The following table highlights some scenarios which may arise when using the RocketRoute integration and can be used for troubleshooting unexpected behaviour: