top of page

The most authentic information resource for pilots, cabin crew and aviation professionals around the world.

5 CA-39 mistakes that get your DGCA logbook rejected


Stylised CA-39 declaration on a dark interface with five common error fields flagged: total flight time, VT aircraft registration, IR renewal date, declared totals against eGCA, and PIC time.

If you have filed a CA-39 and received a deficiency notice, the frustrating part is usually this: your hours were fine. Most CA-39 rejections are not caused by an actual shortfall in flight time. They are caused by formatting errors, category mistakes, and totals that do not line up with what the eGCA system already holds on you. These are avoidable, and they are almost always fixable on resubmission.

This post walks through the five mistakes that show up most often on a CA-39, why DGCA flags each one, and what correct practice looks like. If you are filing for the first time or resubmitting after a notice, the goal is to get the form right before it goes in, not after.

What the CA-39 is and why it matters

The CA-39 is the DGCA logbook declaration form required for licence-related applications, including rating endorsements and renewals. It is the document where you formally declare your flight hours and ratings to the regulator. On the surface it looks like a simple summary. In practice it sits on top of two things that have to agree with each other: your logbook, and the independent record DGCA already holds on you in the eGCA system.

That second point is the one that catches people. eGCA is not only a submission portal. It holds its own record of your hours and ratings, and when your CA-39 declaration does not match that record, the application is rejected. So the CA-39 is less a form you fill from scratch and more a reconciliation: your logbook on one side, eGCA on the other, and the declaration is where the two meet. If you keep a DGCA-ready logbook from the start, this reconciliation is routine. Our DGCA pilot logbook guide covers how to set that up.

The flow below shows the CA-39 submission path and where each of the five common mistakes interrupts it. Four of the five are caught at reconciliation against eGCA. One is caught earlier, at the basic format check. None of them are about whether you actually have the hours.

 Flowchart of the CA-39 submission path showing where five mistakes trigger a DGCA deficiency notice: VT registration at the format check, and time basis, IR date, eGCA totals, and PIC category at eGCA reconciliation.

Mistake 1: block time logged instead of flight time

DGCA hour totals on the CA-39 are based on flight time, measured chock-off to chock-on per the ICAO convention. The mistake here is carrying a different time basis into your totals, usually because a roster export or an airline system records hours on a basis you did not check. Why DGCA flags it: if your declared totals are built on the wrong time basis, every downstream number is off by a consistent margin, and that margin will not match eGCA. Correct practice is to confirm which convention your hours are recorded on, and to keep every entry on the flight time basis DGCA expects, so the total you declare is the total DGCA is checking against.

Mistake 2: aircraft type and registration mismatch

Aircraft registered in India use the VT-XXX format. A registration entered inconsistently, or in a form that does not match the DGCA record, is a known cause of deficiency notices. This is a small field doing a lot of work: DGCA cross-references the registrations in your logbook against its own aircraft records, and a single mismatched or mistyped registration breaks that check.

Why DGCA flags it: the registration is how the regulator confirms the aircraft you flew is the aircraft it has on file. Correct practice is to enter every registration in the full VT-XXX format exactly as it appears on the aircraft documents, and to keep that format consistent across every entry rather than abbreviating some and not others.

Mistake 3: an outdated IR renewal date

Your instrument rating validity and renewal date have to be current and consistent with eGCA at the time you submit the CA-39. The mistake is submitting with an IR date that is stale, or that does not agree with what eGCA shows.

Why DGCA flags it: ratings are time-bound, and the declaration has to reflect your status on the date of submission, not the date you last updated your logbook. Correct practice is to check your IR renewal date against eGCA before you file, and to make sure the date on the declaration matches the current record rather than an older one.

Mistake 4: totals that do not match the eGCA system

This is the mistake underneath several of the others. The eGCA system holds an independent record of your hours and ratings. When the totals on your CA-39 declaration do not reconcile with that record, the application is rejected, even when both numbers are individually defensible.

Why DGCA flags it: the regulator is not only reading your declaration, it is comparing it. A discrepancy between the two is treated as something to resolve before the application can proceed. Correct practice is to reconcile against eGCA before submission rather than after a notice: pull your eGCA record, compare it line by line against the totals you are about to declare, and close any gap first. This is also where the earlier mistakes surface, because a wrong time basis or a miscategorised block of hours shows up here as a total that does not agree.

Mistake 5: PIC time miscategorised

PIC, Co-Pilot (P2), and Dual are distinct categories under DGCA, and hours entered in the wrong category affect your eligibility calculations. The most common version of this is sectors flown as P2 being recorded as PIC, which inflates command time.


Side-by-side logbook hour breakdown showing the same 1,395 hour total split two ways: a miscategorised version counting P2 sectors as PIC, and a correctly categorised version that reconciles with eGCA.


Why DGCA flags it: eligibility for ratings and licence actions is calculated from category totals, not just the grand total. As the comparison above shows, two logbooks can carry an identical total flight time and still differ on what each pilot is eligible for, because the split across PIC, P2, and Dual is different. Correct practice is to categorise each sector at the time you log it, by the role you actually held, so your command time reflects command sectors and nothing else.

How Wingman helps you avoid these mistakes

Wingman is a digital pilot logbook used by more than 30,000 pilots across over 400 airlines, and DGCA is one of the regulators it supports. It does not fill the CA-39 for you. What it does is hold the underlying record in a structure that makes each of these five mistakes harder to make.

You log each sector once, against one flight time figure, rather than mixing block and flight time from different sources. Aircraft type and registration sit in their own fields, so the VT-XXX format stays consistent across your whole history instead of varying from one entry to the next. PIC, Co-Pilot (P2), and Dual are separate fields recorded per sector, so command time stays separate from P2 time and your category totals hold up under the eligibility maths. Currency and validity dates, including your IR, are tracked in one place, so a renewal is something you check before you file rather than discover in a notice. And because Wingman imports directly from rosters including AIMS eCrew, NavBlue RAIDO, CAE Crew Access, ARMS, CESAR, Sabre, FLICA, and PDC CrewConnex, far fewer hours are typed by hand, which is where most registration and categorisation errors begin.

Kept this way, the record is one you can reconcile against eGCA with confidence, because the numbers were clean from the first entry. Wingman runs on iOS, Android, and web, with the same logbook on every device, and the free tier covers up to 250 hours. India pricing is ₹4,499 per year. For the full product detail, see Wingman. For the submission step itself, here is how to upload your logbook to eGCA, and if you are working toward a command upgrade, DGCA ATPL eligibility and the eGCA Auto-Profile Update covers how category totals feed your eligibility.

You can cross-reference official guidance directly on the DGCA website and check your own record on the eGCA portal.

Frequently asked questions

What is the CA-39 form used for in DGCA applications?

The CA-39 is the DGCA logbook declaration form used for licence-related applications, including rating endorsements and renewals. It is where you formally declare your flight hours and ratings to the regulator as part of those applications.

What is the difference between block time and flight time for DGCA purposes?

For CA-39 hour totals, DGCA uses flight time measured chock-off to chock-on, following the ICAO convention. The practical point for pilots is to make sure your declared totals are built on the time basis DGCA expects, rather than a different figure carried over from a roster or airline system.

Why does a VT registration mismatch cause a CA-39 rejection?

Indian aircraft registrations use the VT-XXX format, and DGCA cross-references the registrations in your logbook against its own records. A registration entered inconsistently, or in a form that does not match the DGCA record, is a known cause of deficiency notices, because the regulator cannot confirm the aircraft against its file.

What happens if my CA-39 totals do not match my eGCA records?

eGCA holds an independent record of your hours and ratings. If the totals on your CA-39 declaration do not reconcile with that record, the application is rejected until the discrepancy is resolved. Reconciling against eGCA before you submit is what prevents this.

How do I correct a CA-39 after receiving a DGCA deficiency notice?

Read the notice to identify which part of the declaration was flagged. Compare your logbook and your CA-39 against your eGCA record to find where they diverge. Correct the underlying entries so the time basis, registrations, IR date, category split, and totals all agree with eGCA. Then resubmit the corrected declaration. The aim is to close the specific gap the notice identified rather than refiling the same numbers.

Can I use a digital logbook like Wingman to fill the CA-39?

A digital logbook does not replace the CA-39 form itself. What it does is give you clean, correctly categorised totals that are already consistent with the flight time, registration, rating, and category conventions DGCA checks, so completing and reconciling the declaration is straightforward. Wingman keeps these records structured per sector, which is what makes the totals on the form line up with eGCA.

Start logging in a format DGCA accepts

Most CA-39 rejections come down to records that were not kept in a structure DGCA could reconcile, not hours that were missing. Keeping the time basis, registrations, ratings, and category split clean from the first entry is what turns the CA-39 from a risk into a formality. Start logging in a format DGCA accepts. Try Wingman free.

Comments


bottom of page