How do you report non-safety related operational issues encountered during your rotation?

How do you report non-safety related operational issues encountered during your rotation?

• A. Email supervisor
• B. FACTS
• C. Logbook
• D. Call flight deck

Answer: (B)

Reporting non-safety related operational issues through FACTS keeps the findings centralized, trackable, and assignable to the right teams for timely resolution. This system is designed for crew to log issues that affect day-to-day operations—things like equipment quirks, maintenance delays, scheduling problems, or service deficiencies—so each item enters a formal workflow, receives a case number, and can be trended over time to prevent recurrence. Using FACTS ensures the information is captured consistently and reaches the appropriate operations personnel, with an auditable record for accountability. Emailing a supervisor can miss or derail the formal tracking process, leaving issues less visible and harder to monitor. The logbook is meant for recording flight duties, flight-time records, and safety-critical notes, not for provisioning a structured operational issue with follow-up actions. Calling the flight deck is for in-flight coordination and immediate issues during a flight, not for documenting post-rotation operational problems in a way that ensures proper handling and resolution. So FACTS is the appropriate channel for this type of reporting.

Reporting non-safety related operational issues through FACTS keeps the findings centralized, trackable, and assignable to the right teams for timely resolution. This system is designed for crew to log issues that affect day-to-day operations—things like equipment quirks, maintenance delays, scheduling problems, or service deficiencies—so each item enters a formal workflow, receives a case number, and can be trended over time to prevent recurrence. Using FACTS ensures the information is captured consistently and reaches the appropriate operations personnel, with an auditable record for accountability.

Emailing a supervisor can miss or derail the formal tracking process, leaving issues less visible and harder to monitor. The logbook is meant for recording flight duties, flight-time records, and safety-critical notes, not for provisioning a structured operational issue with follow-up actions. Calling the flight deck is for in-flight coordination and immediate issues during a flight, not for documenting post-rotation operational problems in a way that ensures proper handling and resolution. So FACTS is the appropriate channel for this type of reporting.