The OCC operator is an AI system supervised by the duty officer. Steps of the feasibility flowchart are recorded only for the person holding that role.
| Flight | Route | ETD | ETA | Aircraft | PAX | CTOT | Crew | Feasibility | Status |
|---|
No flights yet. Use “New flight” or tell the OCC in the chat.
Prepared by the OCC operator. Nothing is sent without approval. Sending by email is not connected yet: after approving, copy the text into your mailbox.
Set by the NPFO (OM-C). Airports not listed here are “not classified” in the feasibility flowchart.
| ICAO | Name | Cat. | Approach minima | PPR | Hours | Limitations | Qual. | By |
|---|
People, crew codes and aircraft are managed in ReFuelEU (same database). Here the administrator assigns the OCC roles that decide the steps of the feasibility flowchart: OCC, SALES, NPFO, NPCT.
The person keeps one sign-in and one person ID for all operators, and chooses the operator when signing in. New people (never registered) are created in ReFuelEU, Users.
| Name | Person ID | Role | Crew code | Telegram | OCC roles |
|---|
Fleet
Operational data from AFM / OM-B (edit them in ReFuelEU, Fleet). Blue = not yet checked.
| Registration | Type | Seats | Min runway | Surfaces | Range | Cruise | Max crosswind |
|---|
Everything that changes from operator to operator, from its OM A/B/C/D. Blue = proposed (default or suggested), black = confirmed by a person, with the manual reference. Only the administrator or the NPFO can change them.
Manuals
The operator's manuals loaded for the OCC operator (it searches them and cites the section).
| Manual | Revision | Sections |
|---|
| When (UTC) | Who | Action | Details |
|---|