EASA to GCAA conversion: what European pilots need to know about their logbook

Moving from a European operator to a Gulf carrier is mostly about the things you expect: the type rating, the line training, the move itself. The part that tends to surprise EASA-licensed pilots is the paperwork around their flying history. You hold a valid Part-FCL licence and several thousand hours of clean records, so it feels like the logbook should be the easy part. In practice it is often the item that generates the most back-and-forth, because the General Civil Aviation Authority of the UAE assesses your experience on its own terms, not on the assumption that an EASA-format record is automatically sufficient.

This post covers the logbook-specific side of an EASA to GCAA conversion. It does not cover the full licence conversion process, medicals, or theoretical examinations, all of which you should confirm directly with the GCAA and your incoming airline. The aim here is narrow and practical: what your logbook records need to show, where an EASA-shaped logbook can fall short, and how to prepare a clean export before you submit anything.

Why the logbook question catches European pilots off guard

Under EASA, your logbook lives inside a familiar system. Your records are kept in Part-FCL format, your totals reconcile against your licence, and your national authority recognises the structure without further explanation. Part-FCL is defined in Commission Regulation (EU) No 1178/2011, and most European pilots have rarely had to consider whether their logbook would be read by an authority that does not start from that regulation.

A GCAA conversion changes that. You are presenting your flying history to an authority that sets its own requirements for how experience is evidenced and verified. The hours are the same hours, but the way they are formatted, totalled, and supported has to satisfy a different reader. Across the Wingman cohort at Emirates, Etihad, and flydubai, questions about how existing records translate are a recurring theme during a Gulf transition, which is the gap this post is meant to close.

What the GCAA expects from logbook records

The GCAA is the civil aviation regulator for the United Arab Emirates. Emirates, Etihad, and Air Arabia all operate under GCAA oversight, so a pilot joining any of those carriers is working toward a GCAA licence. Qatar Airways sits under a different regulator, the QCAA, and that distinction matters: a conversion into the Qatari system follows QCAA requirements, not GCAA ones, and the two should not be treated as interchangeable.

For the logbook itself, the GCAA's interest is in experience verification. Pilots converting from EASA to GCAA must meet GCAA requirements for verifying their flight experience, which means your records have to do more than list flights. They have to present totals that hold together, distinguish the categories of time the authority wants to see, and stand up to scrutiny when checked against your licence and other documentation. The exact current requirements are published by the GCAA and can change, so treat the authority's own guidance as the source of truth and confirm the present version before you submit.

How EASA-format logbooks map to GCAA expectations

Most EASA logbooks contain the substance the GCAA cares about. The friction is usually one of presentation and completeness rather than missing flying. The table below sets out the areas where an EASA-shaped record commonly needs attention before it reads cleanly for a GCAA assessor.

Area	How EASA logbooks usually handle it	What to check before GCAA submission
Time categories	PIC, SIC, dual, instrument, night recorded per Part-FCL	Confirm every category the GCAA asks to see is present and clearly labelled, not merged into a single block
Totals	Running totals maintained to date	Confirm totals reconcile exactly with your licence and any official records before submission
Aircraft identification	Type and registration per flight	Confirm type and registration are complete for the full history, including early training
Verification	National authority recognises the format implicitly	Be ready to supply supporting evidence; implicit recognition does not carry across to the GCAA
Format	Part-FCL structure	A clean, structured export that an assessor can read without reformatting reduces follow-up requests

The practical takeaway is that you are not rebuilding your logbook. You are making sure an authority that does not assume Part-FCL can read your history without ambiguity, and that every total you present can be traced and verified.

What a complete logbook export looks like

A logbook export that holds up under review is one where nothing has to be inferred. The assessor should be able to open it, read the entries, and arrive at the same totals you are claiming, without reconstructing anything.

In practice that means each flight entry carries its date, aircraft type and registration, route, and the breakdown of time by category. It means the totals are present, current, and consistent with what your licence shows. It means the categories the GCAA wants are distinguishable rather than collapsed together. And it means the document is structured cleanly enough that the reader does not have to reformat it to make sense of it.

Wingman supports export to PDF with structured flight time totals, which gives you a single, consistent document covering your full history with the category breakdowns and running totals already laid out. To be clear about scope: a Wingman export is structured and complete, but it is not formally approved or endorsed by the GCAA, and no logbook product can promise acceptance on the authority's behalf. What it does is remove the manual assembly work and the arithmetic errors that tend to creep in when totals are compiled by hand.

Digital logbooks in the GCAA context

Keeping a digital logbook has become standard across the EASA cohort, and the question European pilots reasonably ask is whether that record will be accepted on the GCAA side. The honest answer is that acceptance depends on the GCAA's current rules and on the completeness of what you present, not on the medium itself. A digital logbook that produces a clean, structured PDF with verifiable totals is generally easier for an assessor to work with than a handwritten book that has to be transcribed.

What you can control is preparation. A digital logbook lets you produce a consistent export, correct errors before submission, and keep the same record across iOS, Android, and web so you are not reconciling separate copies. For background on the formats Wingman produces for the UAE, see Wingman's GCAA logbook guide. If you are still tidying your EASA-side records first, the EASA digital logbook guide covers that end.

Common logbook-related problems and how to avoid them

A few issues come up often enough to be worth naming directly.

The first is totals that do not reconcile. If your logbook total and your licence total disagree, even by a small margin, that gap will be questioned. Resolve it before you submit, not after.

The second is gaps and missing entries from early training. Records from initial training, especially flying done years ago at a flight school, are the entries most likely to be incomplete. Identify these early and gather whatever supporting documentation you can while you still have access to it.

The third is collapsed time categories. If PIC, SIC, dual, and instrument time are not clearly separated, an assessor cannot confirm the experience the GCAA wants to see. Make sure each category is distinguishable in the export.

The fourth is a record that has to be reformatted to be read. The cleaner and more structured your export, the fewer follow-up requests you are likely to receive.

Preparing your logbook for GCAA submission, step by step

The sequence below is a sensible order of operations. It assumes you will confirm the current GCAA requirements directly before you act on any of it.

Step one is to confirm the current requirements with the GCAA. Everything downstream depends on knowing what the authority asks for at the time you submit, because published requirements change.

Step two is to reconcile your totals. Open your logbook total and your licence total side by side and make them agree.

Step three is to verify each entry. Work through the record and confirm that date, type, registration, route, and time breakdown are complete, paying particular attention to older entries.

Step four is to resolve gaps. Where early training entries are thin, assemble supporting evidence now rather than during the submission.

Step five is to separate your time categories so each one the GCAA wants is distinguishable.

Step six is to produce a clean, structured export. A single PDF with the totals and category breakdowns laid out is easier to assess than a record an assessor has to reorganise. If you keep your logbook in Wingman, you can export your logbook from Wingman directly to PDF.

Step seven is to gather your supporting verification documents, since the GCAA verifies experience rather than taking a total at face value.

Step eight is to submit according to the GCAA's current process, confirmed at step one.

Frequently asked questions

Does GCAA accept digital logbooks for licence conversion?

Acceptance depends on the GCAA's current requirements and on the completeness of what you submit, not on whether the record is digital or handwritten. A digital logbook that produces a clean, structured export with verifiable totals is generally straightforward for an assessor to work with. Confirm the present requirements with the GCAA before you rely on any particular format.

What flight time totals does GCAA typically need to see?

The GCAA verifies flight experience, which means it looks for totals that reconcile with your licence and a breakdown of time by category rather than a single combined figure. The specific categories and thresholds are set by the authority and can change, so check the current GCAA guidance rather than assuming your EASA layout maps across unchanged.

Can I use my EASA logbook PDF export directly, or does it need to be reformatted?

Often the substance is already present, and the work is confirming completeness and presentation rather than rebuilding the record. The export should let an assessor read your entries and arrive at your totals without reformatting. If categories are collapsed or totals do not reconcile, address that before submission.

Does Wingman's export meet the format requirements for GCAA submission?

Wingman produces a structured PDF export with flight time totals already laid out, which removes the manual assembly and arithmetic that cause most errors. It is structured and complete, but it is not formally approved or endorsed by the GCAA, and no product can guarantee acceptance on the authority's behalf. Treat the GCAA's current requirements as the standard your export needs to satisfy.

Is the process different if I am joining Etihad versus Emirates?

Emirates, Etihad, and Air Arabia all operate under GCAA oversight, so the regulator-side requirements for your logbook are the same regardless of which of those carriers you join. Airline-specific document handling can differ, so confirm the details with your incoming airline. Note that Qatar Airways sits under the QCAA rather than the GCAA, so a move there follows a separate set of requirements.

What happens if my logbook has a gap or missing entries from early training?

Gaps in early training records are common and are best resolved before submission. Identify the missing periods, gather whatever supporting documentation you can from your training provider or previous operators, and reconcile your totals so the record holds together. The earlier you do this, the more likely the relevant paperwork is still accessible.

Getting your records ready

If a Gulf carrier transition is on your horizon, the logbook is the part you can prepare well in advance, without waiting on a single requirement to be confirmed. Reconciling your totals, closing gaps in early entries, and keeping a clean digital record now means that when you do confirm the current GCAA requirements, producing a complete export is a short task rather than a scramble.

Wingman runs on iOS, Android, and web, keeps one consistent logbook across all three, and is free to get started. You can begin organising your records today on the Wingman pilot logbook.