ISU Initial Safety Briefing Notes

Safety Culture and Safety Reporting Overview

• Purpose of the briefing: outline safety culture at ISU, safety practices, how to file a safety report, and what safety culture means for students.
• Speakers: Mister Mandarino, Mister Colbert, and Mister Carpenter in the session; emphasis on ADSC and safety procedures.
• Core idea: education and proactive reporting to reduce risk and improve future safety outcomes.

FAA Accident/Incident Reports

• The FAA publishes daily updates on accidents, incidents, and occurrences. The file distinguishes among these categories, though the speaker uses the term “occurrences.”
• How to access: Google the FAA site with the query faa.gov accident incident reports. The feed updates daily except Saturdays and Sundays; Monday updates show elevated numbers.
• Bottom row note: the entry labeled “fatal accidents” refers to the number of fatal accidents, not the total fatalities.
• Practical point: accidents and incidents happen daily, but not all make national headlines; social media can shape public perception of aviation safety.
• ISU has appeared in these reports more than once, underscoring the importance of safety education and risk reduction.

Importance of Ground School and Decision Making

• Ground school in aviation is as important as flight training, if not more so, because good decision making hinges on knowledge and judgment.
• Emphasis on a comprehensive safety culture that starts with daily decisions and preflight planning.

The Go-Around: Definition, Execution, and Decision Point

• A go-around is executed when a decision is made to abort the landing and climb away for another approach.
• Common triggers: traffic conflicts and especially unstable approaches.
• Key insight from experience: the decision to go around is the critical factor to the success of a go-around; many can execute a go-around, but the timing of the decision is what matters most.
• Go-around execution sequence (high level):
  • Power, pitch, flaps, and gear adjustments are part of the process, but the crucial element is the decision to go around.
  • A go-around can occur from as close as a few feet off the ground to hundreds of feet above it; the action is taking off again without touching down.
• FAA data referenced: the highest percentage of accidents occurs during the approach-to-landing phase; about 45% of incidents fall in this phase, with loss of control often stemming from an unstable approach and late go-around decision.
• Real-world example described: an accident involving two flight instructors (one on their first day, one on their last day) that started with an unstable approach and poor prebriefing.
• Root-cause concept: many accidents/incidents can be traced back to a “Swiss cheese model,” where multiple small holes line up to create a path to an accident unless mitigated by safeguards.
  • Visual metaphor: holes in cheese lining up to allow a pencil to pass through; multiple latent failures align to cause an event.
  • The chain often starts with a core prebrief, unstable approach, and then a suboptimal decision-making sequence.

Swiss Cheese Model and Root Causes

• Swiss cheese model explanation: accidents occur when multiple defensive layers fail to catch latent conditions; holes line up.
• In thecornfield/ tailgate example, a poor prebrief and an unstable approach align with other breakdowns to produce a major incident.
• Lesson: robust prebriefs, stable approaches, and timely go-arounds are essential defenses against accidents.

Human Factors and Factors Influencing Go-Arounds

• Influences include:
  • Human factors and continuous experience with unstable approaches
  • Restrictive rules and concepts
  • Loss of focus or hyperfocus
  • Failure to execute a go-around in a timely manner
  • Lack of recognition and inadequate training
  • Communication gaps and other cockpit dynamics
• The list aligns with the idea of avoiding the “dirty dozen” of aviation errors:
  • Lack of communications, complacency, lack of knowledge, distractions, lack of teamwork, fatigue, lack of resources, pressure, and stress
• These factors contribute to unsafe decisions even when individual actions seem small or isolated.

Stabilized Approach: Definition, Criteria, and Real-World Implications

• Stabilized approach definition: the pilot establishes and maintains a constant airspeed and a constant descent rate toward a predetermined point.
• Real-world example given: an approach at approximately $12{,}000$–$13{,}000$ ft? (altitude wording in talk) with a target descent rate of $500\ ext{ft/min}$ and trimmed airspeed; however, when a gust or thermal disruption occurs (e.g., warm air rising from the earth), the airplane may pitch up and airspeed can shift.
• Pilot responsibility: the pilot must adjust pitch and power to maintain the stabilized profile; if not able, a go-around should be executed.
• Consequences of not stabilizing: deviation can lead to a loss of control; the checklist discipline helps prevent this.
• Checklist discipline: do not bypass failures of the checklist and ensure all items are verified to reduce the chance of a misstep during landing.
• Guidance from FAA advisory material: stabilized approach criteria are codified in advisory circulars and require isolation of stable parameters by a specific altitude threshold (see next section for exact numbers).

Stabilized Approach Criteria (FAA Advisory Circular)

• FAA guidance cited: stabilize by a certain altitude depending on weather conditions:
  • In VMC conditions: stabilize by $500\ \text{ft AGL}$.
  • In IMC conditions: stabilize by $1000\ \text{ft AGL}$.
• These criteria are part of the FAA advisory circulars used to assess approach stability during certification and training.
• Practical takeaway: aim to be stabilized by these altitudes; if not stabilized, initiate a go-around rather than attempting to salvage a poor approach.

Traffic Avoidance Technology: ADS-B Stratus and ForeFlight

• Stratus device: an onboard, portable ADS-B out receiver that provides traffic and weather data to the iPad via ForeFlight.
• ForeFlight integration: connect the iPad to Stratus, then link Stratus to ForeFlight to receive onboard traffic alerts and weather data on the moving map.
• Setup overview:
  • Turn on master switch and follow preflight checklist steps to ensure Stratus is loaded.
  • Connect the iPad to the Stratus via wireless settings (select Stratus network).
  • Open ForeFlight, go to the map view, and enable the traffic layer (traffic icon) so onboard traffic alerts appear.
  • If the first connection doesn’t show a green connected icon, close ForeFlight and relaunch; reconnect as needed.
• Capabilities: traffic alerts and weather; moving map displays traffic; ForeFlight can provide audible traffic alerts if a Bluetooth headset is connected.
• Important caveat: do not rely solely on the iPad/Stratus for traffic awareness; visual scan of traffic remains essential for collision avoidance.
• Practical setup tips:
  • Most students will use a Bluetooth-capable headset; you can connect the headset to the iPad to hear traffic alerts.
  • If you don’t have Bluetooth, adapters are available to enable audio alerts.
  • The iPad mini with cellular capability and GPS is recommended for cockpit organization and reliability.

ForeFlight and Stratus Connectivity Details

• How the system looks in ForeFlight: after connection, a green connected icon appears on the map; a dropdown (filter options) allows you to select the traffic icon to enable onboard alerts.
• The Stratus connection is designed to be integrated with your flight planning app (ForeFlight is the standard in this program).
• Practical advice: do not become 100% dependent on the iPad; you must maintain head-up situational awareness and look outside to see actual traffic in the airspace.

Alternate Apps and University Discounts

• ForeFlight is the preferred app; Garmin Pilot and other apps (e.g., FlightPlanGo) can be used by some instructors, but ForeFlight is the standard here.
• University discounts: the program offers ForeFlight discounts for ISU students; the instructor can help add you to the roster for the discount.

Headsets, Connectivity, and Cockpit Organization

• Bluetooth-enabled headsets are recommended for audio alerts from ForeFlight/Stratus.
• If you use adapters, you can connect non-Bluetooth headsets to ForeFlight/Stratus for audio cues.
• The learning curve includes connecting the Stratus to ForeFlight and ensuring the traffic feature is enabled in ForeFlight.
• Preflight checklist item: connect Stratus early in the preflight phase to ensure the device is functional before taxi.

ISU Safety Infrastructure: ADSC, Safety Council, and Safety Programs

• ADSC: Aviation Department Safety Council; a cross-departmental group focusing on safety culture, risk assessment, and incident review.
• ADSC goals: promote safety-mindedness, maintain independence and objectivity in review, and provide recommendations.
• Safety Council roles: review safety reports, advise on improvements, and provide an avenue for safety concerns to be heard.
• Appeals and reporting: the ADSC can act as an appeals body; concerns may be raised anonymously or with direct discussion with safety officers.
• Safety reporting workflow:
  • Submit a safety report via the safety portal (on the ISU system).
  • The safety director and safety officer review the report and may schedule a debrief with the reporter.
  • The chair and the ADSC are notified; corrective actions are developed and tracked.
  • Reports can be submitted anonymously; anonymity is encouraged to promote openness.
  • The reports feed into the Safety Tracker for monitoring by flight hours and activity levels.
• Safety metrics: Safety Tracker compares safety occurrences to flight hours (grouped by month) to contextualize whether a spike is due to more flying hours or a real safety concern.

Safety Management System (SMS) and Procedural Documents

• ISU has formalized an SMS approach, aligned with FAA guidance (SAFOs and related guidance).
• Four components of SMS:
  • Safety Policy: commitment to continually improve safety.
  • Risk Management: determining the need for revised risk controls.
  • Safety Assurance: monitoring safety performance and controls.
  • Safety Promotion: training, communication, and actions to build a positive safety culture.
• ISU has applied for formal safety management with the FAA’s Flight Standards District Office (Indiana/Indianapolis region).
• SAFOs (Safety Advisories for Operators): FAA advisories used to communicate preliminary safety concerns and mitigations following incidents.
• Process flow after a report:
  • File a safe report → safety director and safety officer conduct follow-up → notify ADSC/chair → implement corrective action → share with the reporter when appropriate.
  • If needed, FAA involvement may occur for external reporting.
• Documentation: SOPs (Standard Operating Procedures) are reviewed and revised; the ISU safety SOPs are currently on revision 12 (13th version including original).

Safety Reporting System: Practical How-To

• ISU uses a safety reporting portal (within the ISU system) with an itemized form:
  • Choose report type (e.g., Flight Ops Incident, Hazard, etc.).
  • Date, time, location, mode of flight (ramp/in-flight), weather conditions.
  • Description of what happened; the reporter can be anonymous if desired.
• Rationale: filing a report while the incident is fresh yields richer details and improves the ensuing debrief and corrective actions.
• Philosophy: the aim is to learn from mistakes and improve safety culture, not to assign blame. The goal is to prevent repeats and to strengthen safety practices.
• Post-report steps: automatic emails notify the safety team; the report is reviewed and may be forwarded to external agencies if necessary; the safety tracker tracks outcomes and corrective actions.

Training Operation Safety Audit (TOSA) and Real-World Observations

• TOSA: training operation safety audit; sometimes conducted with external observers (e.g., a guest captain) to observe and record safety performance.
• Past findings highlighted: rush factor, lack of briefing, and inadequate preflight preparation were common contributing factors.
• Recommendations from TOSA: slow down, complete the briefing and lesson plan, prepare for the day, and visualize successful performance to improve outcomes.
• The message: be prepared, practice good briefing, and avoid rushing to reduce risk.

Personal Messages from Instructors and Core Takeaways

• Emphasis on safety as a constant, not just during training sessions; safety is a shared responsibility.
• The instructors shared personal experiences about the consequences of unsafe decisions, emphasizing the human cost and the need to uphold standards.
• Core caution: always fly the airplane first; do not become so focused on the iPad or cockpit systems that you neglect basic piloting.
• Encouragement to seek help, ask questions, and rely on the ISU community to support learning and safety.

Final Reminders and Culture Notes

• Do not let anyone rush you to fly if you are not comfortable or if conditions are unsafe.
• The ISU program has a strong emphasis on learning from mistakes and maintaining a positive safety culture.
• The community is large (about 105 new students in the class) but collaboration and mutual support are encouraged.
• The takeaway: safety is a continuous process that requires attention, preparation, and open communication; stay informed, stay safe, and help each other.

Personal Reflections and Ethical Considerations

• Flying is rewarding but dangerous if standards are ignored; stories of real accidents illustrate that even experienced pilots can err when rushed or poorly briefed.
• Practical ethics: no fear of reporting; reporting is about prevention and improvement, not punishment; anonymous reporting is available to encourage honesty.
• The session closes with a reminder to balance enjoyment of flying with diligent study, teamwork, and adherence to safety standards.

Quick Practical Action Items for Students

• Ensure Stratus ForeFlight setup is complete before taxi: connect Stratus to iPad, enable traffic alerts, and verify the green connected icon.
• Use ForeFlight’s traffic layer as a supplemental tool, but rely on visual separation and ATC instructions as primary guidance.
• Maintain stabilized approaches: aim to be stabilized by $500\ \text{ft AGL}$ (VMC) or $1000\ \text{ft AGL}$ (IMC).
• If an approach becomes unstable, execute a timely go-around and adhere to the power/pitch/flaps/gear sequence.
• File safety reports promptly if you observe or experience hazards or incidents; include time, location, weather, and a detailed description; anonymity is available.
• Leverage the Safety Tracker to understand how incidents relate to flight hours and to track corrective actions.
• Engage with the ISU safety community (ADSC, safety officers) if you have concerns or questions; safety is a shared responsibility.

$ext{Follow-up actions and communications are critical: } ext{If in doubt, fill it out.}$