Pilot logbook rules under DGCA: what actually counts

A pilot logbook looks like the simplest document in the entire CPL process, a page a day, a few numbers, an instructor's initials. In practice it is the record DGCA leans on hardest at application stage, and it is also the record most students get casually wrong somewhere in the middle of training, not through dishonesty but through inconsistent habits picked up before anyone explained what each column is actually for. This guide is about what categories genuinely matter, why the school's record and your own record are not automatically the same thing, and why the logbook you are filling in today is not a document you get to retire once your CPL is issued.

What actually gets logged

A DGCA-relevant logbook is not just a running total of hours flown. It separates flight time into categories because different licence and rating stages have different minimums against different categories, and an examiner or a DGCA official reviewing your logbook at application stage is checking those categories individually, not just the grand total at the bottom of the page.

• PIC (Pilot in Command) time. Time you were the sole manipulator of the controls and the person responsible for the conduct of the flight. As a student pilot, solo flights flown under instructor authorisation are generally logged as PIC time, since you are alone in the aircraft and solely responsible for it, even though you are not yet licensed. This is one of the categories DGCA checks most closely against the CPL hour requirement, so log it consistently and do not inflate it by including time when an instructor was also handling controls.
• Dual instruction time. Time flown with an instructor on board, whether the instructor is demonstrating, supervising, or sharing controls. Dual time needs the instructor's countersignature in the logbook, entry by entry, not as a batch at the end of the month. This is the category that most often gets challenged later if the countersignatures are missing or inconsistent.
• Solo time. Closely related to PIC time but tracked as its own column in most logbook formats, since some licence and rating stages set a specific solo hour minimum separate from the general PIC minimum. Keep solo entries clearly distinguished from dual entries even on days when you flew both.
• Cross country time. Flight between two points that meets a minimum straight line distance and involves a landing at a point other than the point of departure, under a definition set out in the relevant CAR. Cross country time has its own minimum for CPL purposes, and it is one of the categories where students most often misjudge what qualifies, more on that below.
• Night time. Flight conducted within the officially defined night period, logged separately from day flying because night flying has its own minimum hour requirement and its own currency rules later in a pilot's career.
• Instrument time, actual or simulated. Time flown by sole reference to instruments, whether in actual instrument meteorological conditions, under a hood or visor in visual conditions, or in an approved simulator or synthetic training device. Each of these has a different logging convention, actual instrument time in the aircraft, simulated instrument time in the aircraft, and simulator or STD time as its own line, and DGCA treats them differently when checking against requirements, so do not lump them together as one number.

Every one of these categories has a specific definition and, in several cases, a specific minimum hour requirement written into CAR Section 7 and the Aircraft Rules licensing schedule. The definitions and minimums are revised from time to time, so treat any specific number you have seen quoted online, including anything in earlier guides on this site, as something to confirm on the current CAR text and the eGCA portal rather than something to take as permanently fixed.

How this maps to the CPL hour check

When you apply for CPL issue through eGCA, the licensing team is not simply adding up total flight hours and comparing that to a single number. They are checking your logbook category by category against the requirements for that licence, total flight time, PIC time, cross country PIC time, instrument time, and night time each against their own minimum. A candidate can have comfortably more than enough total hours and still be short in one specific category, most often cross country PIC time or night time, simply because training happened to concentrate on other kinds of sorties.

This is why it is worth tracking your running totals by category well before you reach the skill test, not only after it, so a shortfall in one category can be closed with a few targeted sorties rather than discovered as a surprise at the application stage. If you have not sat the skill test yet, the companion guide on what to expect at the DGCA skill test and GFT walks through that stage in detail, and the category totals in your logbook are exactly what gets checked before you are even scheduled for it.

Training-school logbook vs personal logbook

Most students training at a flying school end up keeping two records without necessarily being told to think of them as two separate things. The first is the school's internal record, maintained by the FTO for its own scheduling, billing, and regulatory reporting, often in whatever software or paper format the school standardised on. The second is your personal pilot logbook, the document that is legally yours, that you carry with you, and that DGCA and, later, every employer and every examiner will actually ask to see.

These two records should show the same flights with the same hours in the same categories. In practice they can drift apart, a flight logged slightly differently in the school system than in your own book, a correction made in one record and never carried across to the other, an instructor countersignature obtained in the school system but never physically signed in your personal logbook. None of this is usually deliberate. It happens because a student treats the school record as the "real" one during training and only starts taking the personal logbook seriously closer to the skill test, by which point months of entries need to be reconciled from memory or from scattered training slips.

The better habit is to update your personal logbook the same day you fly, directly from the school's daily record, and to get instructor countersignatures in your own book as you go rather than in batches. Set aside time every few weeks, not just before a major checkpoint, to sit the two records side by side and confirm every entry matches. If a discrepancy surfaces, resolve it immediately with the instructor or the school's chief flying instructor while the flight is still fresh in everyone's memory, not months later when nobody remembers the details of a specific sortie.

Common logging mistakes

• Double counting time. The most common version of this is logging the same flight time under two categories that should be mutually exclusive for that sortie, for instance counting the same block of time as both dual and PIC when only one applies to a given seat and role on that flight. Another version is carrying a running total forward incorrectly and effectively counting a block of hours twice across two logbook pages.
• Missing instructor countersignatures. Dual instruction entries, and in most formats solo entries authorised by an instructor, need to be signed off at the time, not reconstructed later. A logbook full of dual time with no countersignatures, or countersignatures added in a different pen weeks after the flight, is exactly the kind of thing that draws scrutiny at application stage.
• Inconsistent cross country definitions. Students sometimes log any flight that left the local training area as cross country, when the actual definition requires a specific minimum straight line distance and a landing away from the departure point. Sorties that do not meet the definition should not be logged as cross country even if they felt like a cross country flight at the time. Check the current CAR definition rather than assuming a flight qualifies because of how it was briefed.
• Gaps between the two logbooks. As above, a personal logbook that has not been reconciled against the school record for weeks or months is a recipe for discovering a mismatch right when you need the logbook to be clean, at skill test scheduling or CPL application.
• Arithmetic errors in running totals. A logbook is usually totalled page by page, with each page's totals carried forward to the next. A single arithmetic slip early in the book propagates through every later page. Re-check carried-forward totals periodically rather than trusting them by default.

Digital vs paper logbook practicalities

A growing number of flying training organisations now run some or all of daily flight logging through digital systems, tablet-based logging in the aircraft, or a school-wide software platform that generates hour summaries automatically. This is convenient day to day and reduces some of the arithmetic and transcription errors described above.

Where this needs care is at the point DGCA actually verifies your hours for licensing purposes. Historically, and as of writing, verification at application stage has generally expected a properly maintained and signed physical logbook, or an exportable record that preserves the same signed, entry-by-entry structure, rather than accepting a raw digital export with no equivalent authentication. Practice here can vary by FTO and can change over time as digital record-keeping becomes more standard across the industry, so this is worth confirming directly with your flying school and, where in doubt, with DGCA or eGCA, rather than assuming a digital-only record will be accepted without question. The safer approach for most students is to treat a digital system as a convenient day-to-day tool while still maintaining, or periodically printing and having countersigned, a physical personal logbook that stands on its own as the authoritative record.

Why you keep every logbook indefinitely

It is tempting to treat the logbook as a document whose job ends the moment the CPL is issued. It does not. An ATPL application later in a pilot's career again requires total flight time broken down by category, now against a higher set of minimums, and the only way to demonstrate that history is the logbooks accumulated from the very first solo onward. Type rating records, instructor rating applications, and instrument rating renewals all reference historical flight time in the same way.

Airline hiring processes commonly ask for a complete flight time history going back to a candidate's first flight, not just a summary figure, and some carriers or their training partners will ask to physically inspect original logbooks as part of document verification. A pilot who cannot produce early logbooks, because they were lost, damaged, or simply not kept once the CPL was in hand, can find this becomes a genuine obstacle years into a career, well after the original documents would have seemed to matter.

Keep physical logbooks in a stable, dry location, keep scanned or photographed backups of every page as insurance against loss or damage, and treat each completed logbook as a permanent professional record rather than training paperwork. If you are still working through the earlier administrative steps, such as getting your CPL formally issued once the skill test is behind you, the guide on getting your CPL issued on eGCA after the skill test covers what else eGCA typically wants alongside a clean logbook. And if you are still early enough in the process to be thinking about what the whole route costs and how it is sequenced, the overview at the cost of becoming a pilot in India and the general route map at how to become a pilot are useful starting points.

What examiners and eGCA actually look for

It helps to think about your logbook the way the people reviewing it will, rather than only as your own record of what you did. A DGCA-authorised examiner conducting your skill test will typically want to see the logbook well before the flying portion begins, to confirm you genuinely meet the prerequisite hours for the test itself, and again afterward to countersign the check flight. At that point, an examiner looking at a scruffy, inconsistently filled book, with corrections scratched out rather than properly annotated, entries out of chronological order, or category totals that do not add up when checked, is not just seeing an untidy document. They are seeing a document whose reliability they now have to question entry by entry, which slows down what should be a routine check.

At the eGCA application stage, the review is less personal but more mechanical: someone is checking your declared totals in each category against the minimums for the licence you are applying for, and against the flying hours reported elsewhere in your application, for instance by your flying school. Any mismatch between what your personal logbook says and what the school's records say for the same period is the kind of thing that generates a query and a delay, even when the underlying flying was perfectly legitimate. The practical lesson is the same in both settings: a logbook that is internally consistent, properly countersigned, and clearly organised by category saves you time exactly at the two moments when time matters most, the skill test and the licence application.

A correction, when one is genuinely needed, should be made properly, a single line through the incorrect entry, the correct figure written beside it, initialled and dated, never overwritten or blacked out. Multiple corrections clustered around the same date or the same flight are the kind of pattern that draws extra attention, so it is worth getting the entry right the first time rather than relying on being able to fix it later.

A practical logging routine

Most of the mistakes covered above come down to timing, entries made too long after the flight, countersignatures collected in batches, reconciliation left until just before a deadline. A simple routine avoids nearly all of it.

• Log the same day you fly. Details fade fast. A sortie logged the same evening is far more likely to be categorised correctly than one reconstructed from memory a week later.
• Get the countersignature at the time. Ask your instructor to sign dual and supervised solo entries before you leave the aircraft or the briefing room that day, not at the end of the week or the end of the course.
• Reconcile against the school record monthly. Set a recurring reminder, not just a mental note, to sit your personal logbook next to the school's system and check every entry matches, hours and category both.
• Total each page carefully, and re-check the carried-forward figure. An error in a running total early in the book affects every page after it, so it is worth spot-checking totals periodically rather than only when you reach the last page.
• Photograph or scan every completed page. Do this as you go rather than waiting until the book is full, so a single lost or damaged logbook is never a total loss of the record.

None of this is complicated, but it only works as a routine, not as something you catch up on in a rush before a deadline. Students who build these habits from their very first solo flight tend to reach the skill test and the CPL application with a logbook that needs no untangling, which is one less variable to manage at a stage that already has enough moving parts.

FAQ

AviationGrade editorial team

From CAR Section 7, Series B, and the eGCA licensing checklist

We build the DGCA question banks these guides link to. Corrections welcome and credited.