> ## Documentation Index > Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt > Use this file to discover all available pages before exploring further. # AI in Aviation Safety > How PlaneConnection uses AI for pattern detection, anomaly identification, SmartScore, natural language reporting, and hazard prediction. Artificial intelligence is transforming how aviation organizations manage safety. The volume of data generated by modern flight operations \-- safety reports, flight logs, maintenance records, crew schedules, and environmental data -- exceeds what human reviewers can analyze consistently. AI does not replace human judgment in safety management. It augments it, surfacing patterns and anomalies that would otherwise go unnoticed until they contributed to an incident. This page is for safety managers, accountable executives, and anyone interested in understanding how AI is used within PlaneConnection's safety features. For the broader performance monitoring context, see [Safety Performance Monitoring](/en/explanation/safety-performance). For the feature-level overview, see [Modules Overview](/en/explanation/modules-overview). ## Why AI in Safety Management **AI suggestions are advisory only.** Per 14 CFR Part 5, all safety assessments, investigation findings, and risk evaluations require independent human evaluation by qualified personnel. AI recommendations should be used as one factor among many in decision-making, not as the sole basis for any safety, operational, or maintenance action. See [Legal Notices](/en/reference/legal-notices#ai-and-automated-features-disclaimer). Traditional safety management relies heavily on human review. A safety manager reads each report, identifies patterns through experience and memory, and decides where to focus attention. This works at small scale, but it has inherent limitations: **Volume.** As reporting culture matures and report volumes increase (a sign of healthy SMS), the cognitive load on safety managers grows. A safety manager reviewing 10 reports per week can give each one careful attention. At 50 or 100 reports per week, important signals get lost. **Pattern recognition across time.** Humans are excellent at recognizing patterns within a small set of data viewed simultaneously. They are less effective at identifying slow-building trends across hundreds of reports over months or years. A gradual increase in fatigue-related reports during winter operations might not be obvious from week to week but is clearly visible when analyzed across seasons. **Bias.** Human reviewers naturally focus on recent, dramatic, or familiar hazard types. Less dramatic but more frequent hazards -- ground handling issues, communication breakdowns, minor procedural deviations -- may receive less attention despite representing significant cumulative risk. **Connections across domains.** A discrepancy on one aircraft, a training gap in one crew group, and an increase in reports at one airport might seem unrelated when reviewed in isolation. AI can identify correlations across these domains that would require a safety manager to simultaneously hold dozens of data streams in mind. ## How PlaneConnection Uses AI ### Pattern Detection and Trend Analysis PlaneConnection's AI layer continuously analyzes your safety data to identify patterns that might not be visible in manual review. Temporal analysis detects whether certain types of events are increasing or decreasing over time and whether seasonal patterns exist. Category clustering determines whether reports in seemingly different categories are actually describing the same underlying issue. Correlation analysis identifies whether certain combinations of factors (aircraft type, route, crew pairing, time of day, weather) appear together more frequently in safety reports than chance would predict. These patterns are surfaced as **AI Insights** -- proactive notifications that alert safety managers to trends warranting investigation. An insight might note that reports involving communication issues have increased 40% over the past quarter, or that a specific aircraft type is generating discrepancy reports at twice the fleet average. ### Anomaly Identification Anomaly detection identifies data points that deviate significantly from established baselines. This is different from pattern detection -- it looks for the unusual rather than the recurring. Examples of anomalies the system might flag: * A sudden spike in reports from a location that normally generates very few * A crew member whose flight hours pattern is significantly different from peers * A maintenance due item approaching its deadline with no work order scheduled * A report category that has been dormant for months suddenly generating multiple entries Not every anomaly is a safety concern. But each one represents a data point that merits human review -- and human review applied to genuine anomalies is far more productive than reviewing every data point equally. ### Similar Incident Clustering When a safety report is submitted, the AI compares its content against historical reports to identify similar events. This serves two purposes: **Investigation support.** An investigator reviewing a new report can immediately see similar past events -- how they were investigated, what root causes were identified, and what corrective actions were taken. This accelerates investigation and helps ensure consistency. **Trend identification.** If a new report is similar to several recent reports, it may indicate an emerging trend that has not yet been formally identified. The clustering algorithm surfaces these connections automatically. ### SmartScore SmartScore is PlaneConnection's proprietary safety scoring system. It aggregates multiple operational data sources into a composite safety assessment, providing a single, interpretable score that indicates overall safety health without requiring managers to monitor dozens of individual metrics independently. SmartScore operates at both the organizational level (overall SMS health) and the individual pilot level (personal safety profile). Historical tracking shows how scores change over time, providing a trend view of safety management maturity. The scoring methodology, including input weighting and algorithmic details, is proprietary. See the [SmartScore Methodology](/en/reference/smartscore-methodology) reference for score interpretation and band definitions. ### Natural Language Reporting One of the most significant barriers to safety reporting is friction. Complex forms with dozens of required fields discourage reporting, especially for busy operational personnel. PlaneConnection's natural language reporting allows reporters to describe events in their own words -- as they would tell a colleague -- and the AI extracts structured data from the narrative. The reporter writes: "During pushback at KTEB yesterday evening, the tug driver turned too sharply and the towbar disconnected. No damage to the aircraft but the right main gear came within a foot of the terminal building." The AI extracts: event type (ground handling), location (KTEB), time (evening), phase of flight (pushback), equipment involved (tug, towbar), outcome (near miss, no damage), and severity indicators. The reporter can review and adjust the extracted data before submitting. This approach reduces the time to submit a report from several minutes to under one minute, directly addressing the friction barrier that suppresses reporting in many organizations. ### AI Copilot PlaneConnection integrates an AI copilot (ALI) that provides contextual assistance throughout the platform. ALI is aware of the page you are viewing and the data in context, enabling it to provide relevant suggestions without requiring you to re-explain your situation. On the safety side, ALI can help assess risks directly from risk register entries, draft CPA descriptions, and suggest investigation approaches based on similar past events. On the operations side, it provides dispatch suggestions, schedule optimization insights, and operational awareness. ALI operates as a sidebar that can be opened on any page. It shares the same data boundary and permission model as the rest of the platform -- it only accesses data your role permits. ### AI-Guided Onboarding When a new workspace is created, ALI guides the administrator through a conversational onboarding experience that covers five areas: the operation profile (fleet composition, base locations, certificate information), safety team identification (key personnel required by 14 CFR 5.25), SMS program setup (generating 22 Part 5 compliance documents customized with the organization's details), safety performance configuration (40+ SPIs with targets appropriate for the operation size), and a platform tour. The reason this onboarding uses conversation rather than traditional form wizards is that aviation operations are complex enough that a rigid form cannot anticipate every configuration need. Administrators describe their operation in their own words, and ALI extracts structured data from the conversation -- adapting follow-up questions based on previous answers. Any area can be skipped and revisited later. See the [AI-Guided Onboarding tutorial](/en/tutorials/onboarding) for the full walkthrough. ### Document Intelligence PlaneConnection's AI can analyze safety documents -- SOPs, bulletins, manufacturer advisories, and regulatory guidance -- to answer questions in natural language. A safety manager can ask, "What are our procedures for icing conditions in the King Air?" and receive an answer grounded in the organization's actual documents, with source references. This capability extends to regulatory guidance. Questions like "What does Part 5 require for record retention?" return answers drawn from the regulation and relevant advisory circulars, making regulatory knowledge accessible without manual search. ## Responsible AI Principles AI in safety-critical applications demands careful consideration of how it is used and where its limitations lie. PlaneConnection follows several principles: ### Human-in-the-Loop AI in PlaneConnection is advisory, not autonomous. No AI system makes safety decisions independently. AI surfaces patterns, identifies anomalies, and provides recommendations -- but a human safety manager reviews, validates, and acts on those findings. The accountable executive retains ultimate responsibility for safety decisions, as required by 14 CFR Part 5 Section 5.23. This principle applies at every level. AI insights are notifications, not actions -- a human must review and decide what to do. SmartScore is an assessment tool, not an approval gate; a low score triggers investigation, not automatic operational restrictions. Natural language report extraction is proposed, not final, because the reporter reviews and confirms before submission. Similar incident matches are suggestions, not conclusions, and an investigator decides whether the similarity is relevant to the current case. ### Transparency Users can see why the AI reached its conclusions. SmartScore explains which factors contributed to a given score and how much each factor weighted the result. Anomaly detections explain what baseline was used and why the data point was flagged. Similar incident matches show the basis for the similarity assessment. This transparency is essential for trust. Safety managers need to understand AI outputs to make informed decisions about them. An opaque score that cannot be explained is not actionable in a safety-critical context. ### Data Boundaries AI features in PlaneConnection operate within your workspace's data boundary. Your safety data is not used to train models for other organizations. Analysis is performed on your data in your context, and results are visible only to your authorized personnel. This boundary is essential for the same reasons that drive multi-tenant data isolation -- safety data is sensitive, and operators must control who sees it and how it is used. ### Avoiding Automation Bias There is a well-documented risk that humans over-rely on automated systems, accepting AI outputs without critical evaluation. This phenomenon -- automation bias -- is particularly dangerous in safety-critical domains. PlaneConnection mitigates this risk through deliberate design choices. AI outputs are presented as one input among many, not as definitive answers. Conflicting or ambiguous results are clearly flagged rather than hidden, because suppressing uncertainty would encourage the very over-reliance the design seeks to prevent. Users are encouraged to provide feedback on AI accuracy, which both improves the system and maintains the critical engagement necessary to counteract automation bias. Training materials reinforce that AI is a tool to augment judgment, not replace it. ## FTC Guidance on AI The Federal Trade Commission has issued guidance on AI use in commercial applications that emphasizes four principles: truthful claims (organizations must not overstate what their AI can do), transparency (users should understand when they are interacting with AI and how it works), accountability (organizations are responsible for the outcomes of their AI systems, including errors), and fairness (AI systems should not produce discriminatory or biased outcomes). PlaneConnection's AI features are designed with these principles in mind. Safety AI does not make claims it cannot support, explains its reasoning, operates under human oversight, and is continuously evaluated for accuracy and fairness. ## The Future of AI in Aviation Safety AI capabilities in safety management are expanding rapidly. Some areas are already implemented in PlaneConnection, while others represent active development. On the implemented side, **adaptive training** uses AI to adjust content difficulty and review scheduling based on individual performance, employing spaced repetition to maximize retention (see the [Training Module](/en/explanation/modules-overview#training-module)). **AI-guided onboarding** provides conversational setup that generates compliance documents and configures SPIs automatically (see [AI-Guided Onboarding](/en/tutorials/onboarding)). Looking ahead, **predictive risk modeling** aims to use historical data to predict which hazards are most likely to manifest in the near future. **Real-time operational risk assessment** would provide dynamic risk scoring for individual flights based on current conditions (weather, crew fatigue, aircraft status). **Regulatory change monitoring** would automate the identification of regulatory changes that affect your operation. And **cross-operator insights** -- anonymized, aggregated analysis across the industry with explicit opt-in -- could identify systemic risks that are invisible to any single operator. These capabilities represent the evolution of SMS from reactive and proactive to predictive -- using data not just to understand what happened or what might happen, but to anticipate specific risks before they materialize. ## Related How SmartScore and SPIs work together for monitoring. Where AI features fit within the platform. How natural language reporting supports just culture. The risk assessment process that AI insights support.