How to upload your pilot logbook to eGCA: a step-by-step guide for Indian pilots

If you fly for an Indian carrier, the eGCA portal is where your flying record meets your licence. Every renewal, every endorsement, and every rating you hold depends on the hours recorded there matching the hours you have actually flown. When those two numbers disagree, the result is a shortfall, and a shortfall surfaces at the worst possible moment: usually mid-renewal, when you have the least time to fix it.

This guide documents the eGCA logbook upload process from start to finish: what to prepare, how the manual upload works, where pilots most often get tripped up, and how to resolve a mismatch once one appears. It is written to be useful whether or not you use Wingman. There is a section toward the end on Wingman's direct eGCA upload, but the first three quarters of this post stand on their own.

Why eGCA logbook upload matters

The eGCA portal, the DGCA's digital governance system, is the single record of truth for your licence. Your hours, ratings, medical status, and examination history all live there. When you apply for a CPL or ATPL renewal, the system checks your recorded hours against the requirements for that licence or rating. If the recorded total falls short of what the system expects, your application stalls.

This is what pilots refer to as a shortfall. The frustrating part is that a shortfall does not mean you have not flown the hours. In most cases the hours exist; they have simply not been recorded in eGCA in a form the system recognises. A pilot at IndiGo, Air India, Akasa Air, or SpiceJet flying a full roster accumulates hours faster than the portal record updates if uploads are not kept current. The flying is real. The record is behind.

The stakes are straightforward. A routine licence renewal becomes a back-and-forth with the DGCA, and a rating you need current for your next roster block sits in a pending state. None of this is dangerous if you start early, but it is avoidable, and the way to avoid it is to understand how the upload works before you need it to.

Before you begin

A clean upload depends almost entirely on preparation. Most rejected uploads fail because something was missing before the pilot ever logged in, not because of anything that happened during the upload itself.

Have the following ready before you start:

eGCA login credentials — Your registered pilot account on the DGCA digigov portal. Reset the password in advance if you have not logged in recently.

Logbook in CA-39 format — CA-39 is the DGCA-prescribed logbook format. The eGCA system expects logbook data structured to this format for upload compatibility. A logbook that is accurate but not in CA-39 structure can still be rejected.

Complete hour totals — Block time, flight time, PIC time, night, instrument, and cross-country totals, reconciled and current up to your most recent flight.

Aircraft type and registration details — Each entry needs the aircraft type and registration recorded correctly and consistently.

Supporting documents — Keep your physical logbook, training records, and any previous DGCA correspondence accessible in case verification requires them.

A note on CA-39: the format is not a suggestion. It defines which fields exist, what each field means, and how totals are categorised. A logbook kept in a different structure — whether a spreadsheet of your own design or an app that does not export to CA-39 — may contain every hour you have flown and still not map cleanly onto what eGCA expects. Getting the format right before upload is the single highest-leverage thing you can do.

Process specifics on the eGCA portal change as the DGCA issues new circulars. Treat the steps below as the general shape of the process and check the current DGCA circulars for any recent changes to field requirements or accepted formats before you submit.

Manual upload via the eGCA web portal

The manual route is the upload path available to every pilot regardless of how the logbook is kept. The walkthrough below describes the process in general terms. The eGCA interface is updated periodically, so the exact button labels and menu names you see may differ from any description here. Follow the on-screen labels on the live portal as the authoritative guide.

Step 1: Log in to the eGCA portal. Go to the official DGCA portal at dgca.gov.in/digigov-portal/ and sign in with your registered pilot credentials. If your session has been inactive for a long time, you may be prompted to verify your identity or reset your password before proceeding.

Step 2: Open the logbook section. From your pilot dashboard, locate the logbook or licence services area. This is where flight time records are managed and where the upload function lives.

Step 3: Open the logbook upload screen. Within the logbook section, select the option to upload or submit logbook data. The portal will present an upload interface with fields for your logbook file and any associated details it requires.

Step 4: Prepare and select your file. Confirm your logbook file is in a format the portal currently accepts and is structured to CA-39 requirements. Accepted file formats are stated on the portal itself; check what the current upload screen specifies rather than assuming a format will be accepted. Select the file and complete any required fields on the submission form.

Step 5: Review before submitting. Before you submit, check the totals shown against your own records. Confirm block time, flight time, PIC, night, instrument, and cross-country totals are what you expect. A mismatch caught here is a five-minute fix. The same mismatch caught after submission is a reconciliation case.

Step 6: Submit and confirm. Submit the upload and wait for the portal to return a confirmation or acknowledgement. Do not close the browser or navigate away until you see a clear status message. If the portal shows the submission as received or pending review, that is expected; the record then moves into DGCA processing.

A practical point on timing: the portal can time out during a long session. If you are entering or reviewing a large number of records, work in focused blocks rather than leaving the page open for an extended period, and keep your file ready so the actual upload step is quick.

Common errors and how to avoid them

Most upload failures fall into a small number of categories. Knowing them in advance means you can check for each before you submit.

Field mismatches. This is the most common cause of a shortfall that makes no sense to the pilot. The hours are correct, but a field is categorised differently from how eGCA expects it. Block time logged where flight time belongs, PIC time recorded against the wrong leg, or cross-country time not flagged: any of these produces a total that disagrees with the system. The fix is to reconcile your logbook against CA-39 field definitions before upload, so every hour sits in the field eGCA reads it from.

File format rejection. A file that is not in an accepted format, or a logbook that is not structured to CA-39, gets rejected at upload. The portal states which formats it currently accepts. Check that screen before you build or export your file, not after a rejection.

Session timeouts. A long session on the portal can expire before you submit, and an expired session can lose unsaved work. Prepare your file fully before logging in so the upload itself is fast, and avoid leaving the page idle.

Verification failures. Sometimes the upload is accepted but the data does not pass a later verification check, often because totals do not reconcile with what the DGCA already holds, or because a supporting detail is missing. Keep your physical logbook and training records accessible so you can respond quickly if verification raises a query.

The common thread is that almost every one of these is a preparation problem, not an upload problem. A logbook that is accurate, complete, and structured to CA-39 before you log in clears the upload step without drama.

Wingman direct upload

Everything above is the manual process, and it works. It also has a number of places where a small error becomes a shortfall. Wingman's direct eGCA upload exists to remove those steps.

Wingman is a digital pilot logbook used by more than 30,000 pilots across over 400 airlines, including pilots at IndiGo, Air India, Akasa Air, and SpiceJet. It runs on iOS, Android, and the web, with the same logbook on every device. For Indian pilots, the relevant feature here is that Wingman maintains your logbook in a structure aligned to what the DGCA expects and uploads it directly to eGCA, rather than asking you to export a file and submit it

by hand.

The difference is in where the mismatch risk sits. In the manual process, you are responsible for getting every field into CA-39 structure, choosing an accepted file format, and keeping totals reconciled. In the direct upload path, the logbook is already kept in the right structure as you log each flight, so the upload is a sync rather than a reformat-and-submit exercise. The manual steps that produce field mismatches and format rejections are not steps you take.

Wingman also supports roster import from the systems Indian carriers use, so the underlying flight data is captured accurately in the first place, before it ever reaches eGCA. Wingman has a free tier covering up to 250 hours, and the full version is priced at Rs 4,499 per year for pilots in India. You can read more about how Wingman handles DGCA requirements in the DGCA pilot logbook requirements in India guide.

What to do when there is a mismatch

If a shortfall or mismatch has already appeared, the situation is recoverable. Work through it in order rather than reacting to the alert.

Identify what disagrees. Compare the eGCA record against your own logbook line by line for the period in question. The goal is to find the specific category that disagrees: total time, PIC, night, instrument, or cross-country. A shortfall is almost always concentrated in one or two fields, not spread evenly.

Confirm the cause. Once you know which field disagrees, determine why. The usual causes are the field mismatches and categorisation errors described earlier. Establish whether the hours are missing from eGCA entirely or are present but categorised differently.

Assemble supporting documents. Gather your physical logbook, training records, and any DGCA correspondence that evidences the disputed hours. If you need to demonstrate that hours were flown, the supporting record is what does it.

Correct and re-upload. Where the cause is a categorisation or format error, correct it in your logbook so the field structure matches CA-39, then re-upload. Where hours are

genuinely missing from the record, add them in the correct fields and submit.

Escalate if it does not resolve. If the mismatch persists after a corrected upload, raise it through the DGCA. Contact the relevant DGCA office with your supporting documents and a clear summary of the discrepancy. Keep a record of the dates and totals in question so the conversation stays specific.

The reassuring point is that a shortfall is an administrative problem, not a judgement on your flying. Pilots resolve them regularly. Starting early, before a renewal deadline, is what keeps the process calm.

FAQ

What is the eGCA portal and why do I need to upload my logbook there?

The eGCA portal is the DGCA's digital governance system and the official record of your licence, ratings, hours, and examination history. Your logbook hours need to be reflected there because the system checks your recorded hours against licence and rating requirements during renewals and applications. If the portal record does not reflect the hours you have actually flown, the system flags a shortfall and your application stalls until the record is reconciled.

What logbook format does eGCA accept, and what is CA-39?

CA-39 is the DGCA-prescribed logbook format. It defines which fields a logbook entry contains, what each field means, and how totals such as block time, flight time, PIC, night, instrument, and cross-country are categorised. The eGCA system expects logbook data structured to CA-39 for upload compatibility. As for file formats, the portal states which it currently accepts on the upload screen itself, and that should be checked directly before you build or export your file, since format requirements can change with DGCA circulars.

Why does my logbook show a shortfall on eGCA even though my hours are correct?

his is the most common and most frustrating shortfall. In most cases the hours are real and have been flown; they have simply been recorded in a way the system does not read as expected. The usual cause is a field mismatch — hours categorised against the wrong field, for example block time recorded where flight time belongs, or PIC time logged against the wrong leg. The total then disagrees with what eGCA expects. The fix is to reconcile your logbook against CA-39 field definitions so every hour sits in the field the system reads it from.

How long does it take for eGCA to reflect uploaded logbook hours?

Processing timelines on the eGCA portal are set by current DGCA circulars and can change, so this guide does not state a fixed number of days. After a successful upload the record typically moves into a pending or under-review state before it is reflected. The practical takeaway is to upload well before any renewal deadline rather than close to it, so there is time for processing and for resolving any verification query that arises.

Can I upload my Wingman logbook directly to eGCA?

Yes. Wingman maintains your logbook in a structure aligned to DGCA requirements and uploads it directly to eGCA, rather than requiring you to export a file and submit it manually. Because the logbook is kept in the expected structure as you log each flight, the upload is a sync rather than a reformat-and-submit exercise, which removes the manual steps where field mismatches and format rejections usually occur.

What should I do if my eGCA upload is rejected or stuck in pending?

First, identify the cause. A rejection is usually a file format or field structure issue, so check that your file is in a currently accepted format and structured to CA-39. A submission stuck in pending is often just normal processing; give it time before treating it as a problem. If a genuine mismatch is involved, compare the eGCA record against your logbook line by line, find the field that disagrees, correct it, and re-upload. If it still does not resolve, escalate to the relevant DGCA office with your physical logbook and supporting documents.

Keeping the record current

The eGCA upload is not difficult, but it rewards preparation and punishes improvisation. A logbook that is accurate, complete, and structured to CA-39 before you log in clears the process without incident. A logbook that is reconciled only when a renewal is already due is where shortfalls come from.

For the wider picture on DGCA logbook compliance, the CPL renewal guide for Indian pilots covers how the upload fits into the full renewal process.

If you fly for an Indian carrier and want to skip the manual process entirely, Wingman syncs your logbook directly to eGCA. Start free at wingmanlog.in.