A crew member
Read the apps and data and privacy: which app you have, what it costs you, and what your airline can and cannot see.
Hawk & Mason
What each app and product is, what it is for and how to start, in one place.
Written for three readers: a crew member who wants to know what the app does and what the airline sees, an airline department that wants to know what it would use, and an IT team that wants to know how it connects. Each answer says what is built today and nothing more.
Read the apps and data and privacy: which app you have, what it costs you, and what your airline can and cannot see.
Read the platform and the portal, then your product: Insight, Safety, Academy or Library.
Read buying one module and connecting your systems and data and privacy. Every endpoint is in the API reference.
Crewops is the App Store app for individual crew members: roster, FTL limits, fatigue and logbook. Crewops Crew is the company edition of the same app, which an airline gives to its crews and which opens with the airline's crew code.
Crewops is on the App Store with a free version and an optional subscription, Crewops Pro. The App Store shows the current price in your country before you subscribe.
Each product is licensed separately, per airline. Ask us for a price for your operation at hello@hawkmason.com.
Their roster and the products their airline holds, and nothing else. If the airline holds Safety but not Academy, crews see a Safety tab and no Academy.
The airline side of Crewops: four products licensed separately, Crewops Insight for roster fatigue assessment, Crewops Safety, Crewops Academy and Crewops Library. What an airline buys is what opens, for its departments and its crews.
The operator code, one per airline, signs your departments in to the operator portal at hawkmason.com/crewops/portal and opens the products you hold. The crew code is what your crews enter in Crewops Crew; it opens the crew side of the same products and never opens operator data.
The first page of the portal: one list, across the products you hold, of what needs action now. It shows safety reports near or past their 72-hour clock, overdue actions and findings, open intolerable risks, expired or missing qualifications, notices, courses and revisions past their date, and very tired crew ratings. Each line opens its record.
Your airline gets an operator code for the portal and a crew code for a group of your crews. The crews install Crewops Crew from a link, enter the code, and the products open. Nothing has to be integrated on day one.
It assesses the fatigue of a roster in the browser, and shows the post-flight ratings crews have chosen to share beside it. Ratings from the last 7 days that say very tired (Samn-Perelli 6–7, KSS 8–9) also appear on the Today board.
No. It reads a roster and assesses it; it is not a rostering or pairing optimiser and not an operations control tool. Your rostering system and your own fatigue risk management stay in charge.
Sixteen kinds of report: twelve safety reports, from flight operations to commander's discretion, and four operational ones. The flight is filled in from the roster, a report can be anonymous, carry up to 4 photos and be written offline, and the reporter follows its status and reads the reply.
Yes, through the web report link your safety office shares on its own channels, such as the crew portal, e-mail or a QR code in the crew room. The page is in English and Turkish, offers every report kind except commander's discretion, takes photos, can be sent anonymously and has a follow-up page for the reply. The office can replace the link at any time, and the old one stops working.
No. Your safety office exports an ECCAIRS E5X file, per report or for all reports marked mandatory reportable, and uploads it to the ECCAIRS 2 reporting portal or to its authority's ECCAIRS-based system. The operator, aircraft model and aerodrome codes are completed there.
It classifies reports, records investigations, and keeps a risk register on the ICAO Doc 9859 5×5 matrix, audits and findings with the levels of ORO.GEN.150, management of change and indicators. These features are built around those rules; your own procedures and records prevail.
Read-and-sign notices, qualification records with their expiry dates, and courses. A qualification matrix shows every crew member against every qualification as expired, missing, expiring within 30 days or valid, against role requirements you can edit.
Lessons are video, PDF or a link, and crews can download them to study offline. Exams are graded on the server with a pass mark, so the answers never reach the phone, and every attempt is kept. A course is either required with a due date or self-study, and a certificate appears on the phone when the course is done.
Yes, SCORM 1.2 and 2004 packages are imported from the portal. The phone keeps the package offline and plays it in the app, and the module's own result completes the course. Bookmark and progress are kept on the phone between sessions.
It puts your manuals, procedures, bulletins and forms on the crew phone under a code such as OM-A. Each new revision replaces the current one with its change log, the history is kept, and a revision can ask crews to read and confirm it by a date.
Only your paired crews and your operator code. PDFs are kept in your airline's store, served to no one else, and work offline on the phone once downloaded.
Yes. Each product works on its own and can plug into the systems you already run. Safety even works without rolling out the app, through the web report link.
Through the API, with an API key made in the portal for each system: your SMS, HR, training or document system. A key opens the same products and has the same expiry as your operator code, and it cannot make other keys or change the webhook. Every endpoint is documented at hawkmason.com/crewops/api.
A signed POST to one https endpoint you set, when a safety report is created or updated, a notice is signed, a course is completed or a revision is confirmed. Each delivery is signed with HMAC-SHA256 and tried once with a 5-second timeout and no retries; the portal has a test button and lists the last 20 deliveries.
Safety exports CSV with the Annex I fields and ECCAIRS E5X files. Academy imports qualification records by CSV or the API, exports them as CSV, and imports SCORM 1.2 and 2004 packages. Library takes PDFs, uploaded in the portal or published from your document system through the API.
No. The portal signs in with your airline's operator code, and your systems use API keys. If your IT policy needs single sign-on, ask us at hello@hawkmason.com.
It does not build rosters or pairings, run operations control or plan flights, and it does not submit reports to an authority on your behalf. It holds no approval or certification from any authority; your procedures, records and approved systems prevail.
Your departments, with your operator code in the portal, and your systems, with API keys made from it. Every record is kept for your airline alone, and a code from another airline does not open it.
No. The crew code never opens operator data: not other crew members' reports, ratings, records or confirmations. A crew member's code is paired with one phone, so typing a colleague's code does not open their records.
An anonymous report carries no crew code. The reply still comes back to the phone that sent it, so the safety office can ask for more and the reporter can answer.
No. Your sleep entries, fatigue self-ratings and other health entries stay with you. Only what you send yourself reaches your airline: a post-flight rating with the flight it belongs to, if you switch sharing on and your airline runs Crewops Insight, and a report you file, such as a fatigue report. The details are in the privacy policy.
Write to us. One developer reads it and answers within a working day, in English or Turkish.
Crewops is independent software by Hawk & Mason Studios. Regulation references say which rules a feature is built around; they are not a statement of approval by any authority. Your procedures, records and approved systems prevail.