Disclaimers

1. Regulatory Authority

The Federal Aviation Administration (FAA) is the sole authority for aviation regulation in the United States. PreBrief does not replace, override, or supplement FAA guidance, regulations, or authorizations. All regulatory references (14 CFR Part 107, Part 89, etc.) in the Service are for informational purposes only.

Regulations may change. PreBrief's rule engine is updated periodically, but there may be a lag between regulatory changes and system updates. Always verify current regulations at ecfr.gov.

2. Airspace Authorization

PreBrief does not file, submit, process, or grant airspace authorizations of any kind. It is not a LAANC provider and is not an FAA-approved UAS Service Supplier (USS).

When controlled airspace is detected, the Service may provide links to FAA-approved USS providers (Aloft, DroneUp, Airspace Link, etc.) for the operator's convenience. These are outbound links only — PreBrief has no integration with, endorsement of, or responsibility for these third-party services.

3. Weather Data

Weather information displayed in PreBrief is sourced from NOAA (aviationweather.gov), Open-Meteo, and the HRRR model. This data is provided for planning purposes only.

• Weather conditions can change rapidly and without notice
• METAR observations are typically 20–60 minutes old
• Model-derived data (wind profiles, CAPE) has inherent uncertainty
• Local microclimates may differ significantly from reported station observations

The RPIC must independently assess weather conditions at the time and place of flight using official FAA-approved sources (1800wxbrief.com, aviationweather.gov).

4. NOTAM and TFR Information

NOTAMs (Notices to Air Missions) and TFRs (Temporary Flight Restrictions) displayed in PreBrief may be incomplete, delayed, or unavailable due to upstream FAA system limitations.

The RPIC is required by 14 CFR § 91.103 to review all available NOTAMs and TFRs before flight. PreBrief's NOTAM display does not satisfy this regulatory requirement — operators must independently verify at NOTAMSearch.faa.gov or 1800wxbrief.com.

5. Airspace Data Currency

Airspace boundaries, UASFM grid ceilings, Special Use Airspace, and airport data are derived from FAA published datasets and are refreshed periodically. This data may not reflect:

• Recent airspace reclassifications (effective but not yet ingested)
• Temporary airspace changes (TFRs, NOTAMs)
• Active military operations areas (MOA activation status)
• UASFM grid changes published between our refresh cycles

Each brief displays the airspace data version used. Users should verify data currency before relying on airspace assessments.

6. Vertical Industry Overlays

Industry-specific overlays (NERC-CIP for bulk electric systems, NESC MAD for transmission lines, TIA-222 for telecom towers) are advisory in nature. They are intended to surface awareness of specialized requirements — not to provide definitive compliance guidance.

Operators working on specialized infrastructure must consult with facility operators, subject-matter experts, and applicable industry standards independently.

7. Equipment Database

Aircraft specifications, sensor data, and battery information in the equipment database are sourced from manufacturer publications and may not reflect:

• Firmware updates that change aircraft capabilities
• Modified or aftermarket equipment configurations
• Individual aircraft condition, maintenance status, or modifications
• Regional or regulatory variants of aircraft models

The operator is responsible for verifying that their specific aircraft meets the requirements indicated by the preflight assessment.

8. Evidence Pack PDF

The Evidence Pack PDF is a documentation aid. It records the state of the assessment at the time of generation. It does not:

• Constitute proof of regulatory compliance
• Satisfy any specific FAA documentation requirement
• Replace the operator's own preflight records
• Guarantee that conditions remain unchanged between generation and flight

Operators using the Evidence Pack for client or insurer documentation do so at their own discretion and risk.

9. No Machine Learning in Regulatory Decisions

All compliance evaluation logic in PreBrief is deterministic and rule-based (OPA/Rego policy engine). No machine learning, AI prediction models, or probabilistic algorithms are used in the regulatory decision path. Every finding is traceable to a specific rule ID and data source.

10. Third-Party Links and Services

PreBrief may contain links to third-party websites and services (FAA, NOAA, USS providers, equipment manufacturers). We are not responsible for the content, accuracy, or availability of these external resources.

11. Verify Before Flight

PreBrief assessments are generated in advance of the flight. Conditions — airspace, weather, NOTAMs, TFRs, ground activity — can change between assessment generation and actual flight time. The RPIC must re-verify all conditions on the day of flight using official sources before launching.