The remote pilot in command (RPIC) must confirm the serviceability status of an RPA after each mission
After the last flight of a mission, the Remote Pilot in Command (RPIC) is prompted to declare the RPA either serviceable or unserviceable. This action helps to maintain a record of the RPAs condition and suitability for operations. If an RPA is declared as 'unserviceable' at the end of a mission, it will be flagged in the app and a maintenance request will be generated.
Note: If you planned mission involves multiple RPAs, you will be prompted to mark each RPA as serviceable or unserviceable at the conclusion of your mission.
Serviceability Declaration (Field App)
The serviceability prompt comes after the Remote Pilot selects 'End All Flying' in the post-flight screen. The first step is to declare the RPA serviceability. If serviceable is selected, the RPIC will be able to complete the mission as normal. If unserviceable is selected, a reason needs to be entered for this. The mission can now be completed.
Once the mission has been completed, it appears in the Office App with the status completed.
Mission Record (Office App)
At this point the RPIC can still make edits to the serviceability declaration as the mission has not yet been finalized.
At this point a maintenance request has been created, with a draft status.
Once any required edits have been made, pressing the submit button (above) will create a maintenance request for that RPA. The maintenance request will show up under the maintenance widget accessible from the FlyFreely dashboard. The maintenance controller will also be notified of the request so that an inspection can be undertaken along with any required repairs.
Looking at the RPA details (via the RPA widget) shows that our Inspire 1 is now marked as unserviceable. The aircraft will have this status until the maintenance task is completed and the maintenance controller has returned the RPA to serviceable status.