Guide

  1. Register
    1. Add Aircraft (aka asset)
    2. Add API Key
    3. Add Tour / Flight Codes  (This comes from the same template already used for reporting)
  2. Operator Reporting Assistant Tool (Tool) sends to filter
    1. Filter formats the query to pull from AL-PRO using the API key given to pull flights
  3. Alpro receives the request
    1. Returns flights with relevant. codes
    2. Then sent back to filter
  4. Filter validates and removes extra data
    1. Filter will go through and validate tour / flight code
      1. If invalid tour / flight code, will simply disregard (no data will be saved or processed for these codes)
      2. Grabs departure times, aircraft, ALpro code
  5. Sends the information in step 4 including IMEI and tail number to Sky connects (Spidertracks)
    1. Sky connects sends the Tool geospatial information relevant to the requested times, flights, aircraft, and etc.
    2. Sends back to filter
  6. Receives skyconnect data and prepares to matching process with data from step 4
    1. Validates based on aircraft, date, flight num (if applicable)
    2. If they do not match based on tour / flight code requested
      1. We ignore the data, and it will NOT be saved.
    3. If matches, send back to Tool
  7. Operator Reporting Assistant Tool then receives the matching flights, and geospatial data, and saves the information into a database.
  8. It then can
    1. Automatically send every 6 months to FAA/NPS
    2. Manually be sent by the operator to FAA/NPS
      1. Validates and remove any unwanted data from the system

API Log: