{"id":4948,"date":"2026-10-10T18:04:00","date_gmt":"2026-10-10T22:04:00","guid":{"rendered":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/event-report\/what-happens-if-you-do-not-answer\/"},"modified":"2026-10-10T18:04:00","modified_gmt":"2026-10-10T22:04:00","slug":"what-happens-if-you-do-not-answer","status":"publish","type":"docs","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/event-report\/what-happens-if-you-do-not-answer\/","title":{"rendered":"What happens if you do not answer"},"content":{"rendered":"\n

Your organization sets a number of days to answer an event report (for example 7 days<\/strong>). The delay is counted from the Written the<\/strong> date of the report. Once this delay is passed without an official answer (Save and Request evaluation<\/strong>), several things can happen.<\/p>\n\n\n\n

Restrictions on activities<\/h2>\n\n\n\n
Restriction<\/th>Effect<\/th>Where you see it<\/th><\/tr><\/thead>
No scheduling allowed<\/strong><\/td>You can no longer be scheduled for activities (for example flights or lessons) until you answer.<\/td>Red bar on your profile, red calendar icon in the report.<\/td><\/tr>
No activities allowed<\/strong><\/td>You can no longer start an activity: the ramp out of a flight record is refused with the reason “Event not close after \u2026 days”.<\/td>Red bar on your profile, red table icon in the report.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

These restrictions apply to all members<\/strong> concerned, students and staff alike, unless the sender checked “Activities allowed”<\/strong> on that report. They are removed as soon as you click Save and Request evaluation<\/strong> (or when the report is evaluated or closed).<\/p>\n\n\n\n

\"Member<\/a>
Member profile with the red bars "No scheduling allowed" and "No activities allowed"<\/figcaption><\/figure>\n\n\n\n

Example:<\/strong> an event report is written on September 30 and your organization allows 7 days. On October 7 you have not answered. From that day, your instructor can no longer book you on the schedule, and if you try to ramp out from a flight record, it is refused. You answer on October 10 with Save and Request evaluation<\/strong>: the restrictions are removed immediately and you can be scheduled again.<\/p>\n\n\n\n

Home page lock<\/h2>\n\n\n\n

When your organization activates it, members with an overdue event report (not answered within the delay) or an overdue assigned action are locked on the home page<\/strong>: every other page sends you back to the home page. The Event report center<\/strong> stays available, so you can always open the report and answer it.<\/p>\n\n\n\n

On the home page, the Important reminders<\/strong> pop-up lists what you have to do:<\/p>\n\n\n\n

\"Important<\/a>
Important reminders pop-up listing "N.4024, You need to provide an answer" with the restriction warning, and an "Action overdue since" line with "Initiate by"<\/figcaption><\/figure>\n\n\n\n
Line<\/th>Meaning<\/th><\/tr><\/thead>
N.xxxx, You need to provide an answer<\/strong><\/td>Report number xxxx is waiting for your answer. The grey warning reminds you that you may be restricted from scheduling or activities. Click the number to open the report in a new tab.<\/td><\/tr>
N.xxxx, Action overdue since <date><\/strong><\/td>An action assigned to you on this report has passed its projected date. Initiate by<\/strong> shows who asked for it.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If you believe you are locked by mistake, or you cannot complete an action, contact the initiator<\/strong> of the report, as the pop-up says.<\/p>\n\n\n\n

On the mobile version and the app<\/h2>\n\n\n\n

On the mobile version, a Locked reminders<\/strong> pop-up tells you that you have pending items related to an event report or a QA report and that some features are disabled. Answering is done from the desktop version<\/strong> of AirSupervision: open it on a computer (or in your phone’s browser in desktop mode), answer the report, and the mobile features are available again.<\/p>\n\n\n\n

\"Mobile<\/a>
Mobile home page with the Locked reminders pop-up<\/figcaption><\/figure>\n\n\n\n

Exceptions set in your profile<\/h2>\n\n\n\n

The lock and the restrictions can be disabled for some members:<\/p>\n\n\n\n

    \n
  • On the report:<\/strong> the sender can check Activities allowed<\/strong>, so this report never restricts your activities.<\/li>\n\n\n
  • In your profile:<\/strong> an administrator can grant the option “Can never be locked for overdue events (SMS, QA)”<\/strong>. With it, you are never locked on the home page for overdue event or QA reports. You still have to answer them, and the scheduling and activity restrictions above still apply unless Activities allowed<\/strong> is checked on the report.<\/li>\n\n\n
  • Administrators with the highest access level are never locked on the home page.<\/li>\n<\/ul>\n\n\n\n

    Checklist<\/h2>\n\n\n\n
      \n
    • \u2610 I open every event report addressed to me as soon as I receive the alert.<\/li>\n\n\n
    • \u2610 I write a factual answer: what happened, contributing factors, what I will do.<\/li>\n\n\n
    • \u2610 I click Answer \u203a Save and Request evaluation<\/strong> (a draft is not an answer).<\/li>\n\n\n
    • \u2610 I complete any action assigned to me before its projected date.<\/li>\n\n\n
    • \u2610 If I am locked or restricted, I answer the report or contact the initiator.<\/li>\n<\/ul>\n\n\n\n

      Sources for the SMS summary<\/h2>\n\n\n\n
        \n
      • ICAO Annex 19 \u2014 Safety Management, and ICAO Doc 9859 Safety Management Manual (four SMS components: safety policy and objectives, safety risk management, safety assurance, safety promotion).<\/li>\n\n\n
      • Industry just-culture and non-punitive reporting policies (for example NAV CANADA’s Just Culture program).<\/li>\n<\/ul>\n","protected":false},"featured_media":0,"parent":4945,"menu_order":2,"template":"","doc_tag":[],"_links":{"self":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/4948"}],"collection":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/types\/docs"}],"version-history":[{"count":0,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/4948\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/4945"}],"prev":[{"title":"Answering an event report","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/event-report\/answering-an-event-report\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/4947"}],"wp:attachment":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/media?parent=4948"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/doc_tag?post=4948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}