Skip to content
Documentation
Archive
Product Manuals (Drafing Area)
RPIC Station AE Manual
3. Normal Procedures
Aircraft Starting
Aircraft Starting

Aircraft Starting

Andi Lamprecht Andi Lamprecht ·· 4 min read· Draft

The Aircraft Starting of the RPIC Control Station can be undertaken by an RPIC-delegated member of the flight crew or the RPIC themselves, with final responsibility of the functionality and status of the RPIC Control Station Starting procedure falling on the RPIC.

When using HubOps, delivery mission execution is required. When using Uncrew Mission Planner, both delivery missions and route missions can be executed.

NOTE: After a ground soak period at cold temperatures, the aircraft should not be operated for 5 minutes after aircraft power is applied. Failure to comply may result in failure of Aircraft Starting and/or Before Takeoff checks.
  1. Radio Comms: This step is only required if operating with a flight crew of greater than one (1). If applicable, transmit voice communication over the droneport’s configured radio communication channel and confirm that all devices in use receive the transmission. This step should be repeated on each voice communication device in use.

For each voice communication device in use, ensure that adequate energy life for the device is available. Inspect each device to ensure the battery is not leaking and that there is no damage impairing operation, such as broken dials, buttons, antennas, or speakers.

  1. AMC GCS: Connect to the aircraft through the Comm Links tab on the RPIC Tablet.

  2. Uncrew GCS: Confirm the Uncrew Mission Manager and Mission Console are open on the RPIC Control Station. Select the appropriate droneport location on the Mission Manager and “Start Shift” on the Mission Console.

  3. Flight Alerter: Select and open the Flight Alerter application on the RPIC Control Station.

  4. Kp-index: Confirm at 8 or less. If greater, STOP. Do not fly while conditions persist

  5. AMC GCS: Confirm that the Remote ID status indicator (top right corner of the Fly View screen on the RPIC Tablet) is green. Confirm the number of satellites exceeds 21.

  6. Hub Dashboard (Hub Status Monitoring Cloud-based Software): On the RPIC Control Station, visually inspect the Hub Status Monitoring screen (also referred to as the Hub Dashboard). This should be located on the RPIC Control Station LCD screen. Confirm that all statuses are “GO” on the dashboard as illustrated in Figure 1-135.

CAUTION: Do not proceed if any of the indicators are “NO GO”. This indication will be presented in accordance with Figure 1-137. This indicates conditions are not acceptable for flight. Wait until next 15 minute refresh. If the status continues at this time to indicate “NO GO”, submit a Maintenance ticket in accordance with the UMM.

  1. HubOps MCA: If applicable, perform the steps detailed in the HubOps MCA - Pick, Pack, Flight deck, and Initial Piloting normal procedures provided in Section 3.3.5. Each procedure should be conducted in the order they are presented. The procedures are documented after the RPIC Control Station Starting procedure to avoid continuity issues with the performance of the RPIC Control Station Starting normal procedure.

  2. Soft Reboot: If the HubOps MCA is not used, perform Aircraft Soft Rebooting procedure as per Section 3.3.4.

  3. AMC GCS: Open MAVLink messages and confirm PLD is idling.

  4. AMC GCS: Select the battery icon (top right corner of the Fly View screen on the RPIC Tablet) and verify voltage is greater than 49.5V and energy consumption (mAh) is nominal (consumption should be relatively equal).

NOTE: If the energy storage device voltage is below 49.5V or the energy consumption is not nominal, do not proceed. Restarting Aircraft procedure should be performed. If issue(s) persist, alternative energy storage devices should be utilized and the Aircraft Power procedure repeated. Maintenance should be performed on the removed energy storage devices in accordance with the PRISM V2.3 UMM.

  1. Uncrew Mission Planner: If applicable, build and create a mission. Ensure at a minimum a takeoff, landing, and delivery point (or waypoint) objectives are designated within the mission. A delivery point objective shall not be included when conducting a route mission.

  2. ASMIRA: Connect to aircraft through the web client. Confirm that the video stream is operational by its display in the web client.

Last updated on
Aircraft PowerRestarting Aircraft