The provision in one view
Section 162 of the Bharatiya Nyaya Sanhita, 2023 punishes abetting an assault by an officer, soldier, sailor or airman in the Army, Navy or Air Force of the Government of India on any superior officer being in the execution of his office -- where the assault is actually committed in consequence of that abetment. The punishment is imprisonment of either description for a term which may extend to seven years, and the offender is also liable to fine S1; S4.
It is the result-based twin of section 161. The conduct described is identical; the only difference is that the abetted assault has in fact followed, and the maximum rises from three years to seven S1; S8.
Its predecessor is section 134 of the Indian Penal Code, 1860 S2. The comparison returned 1.0000 -- a perfect match, with no differences at all in the operative text.
Five findings:
- The First Schedule assigns this seven-year offence to a Magistrate of the first class, whose sentencing power is three years. That mismatch is the central subject of this article -- and it is not an isolated slip, because the Schedule makes the same allocation for several other seven-year offences.
- The same entry also leaves the fine beyond the assigned Magistrate's reach, so both limbs of the problem appear together.
- The text is unchanged from the Penal Code -- the fifth perfect match in this collection.
- The marginal notes produce a third variant, and the First Schedule's version is ungrammatical and matches neither the Penal Code nor the Sanhita.
- The one judicial statement that exists on the predecessor is about this section, not section 161 -- although the Court cited a different section number while describing it.
The exact words
162. Abetment of such assault, if assault committed. Whoever abets an assault by an officer, soldier, sailor or airman, in the Army, Navy or Air Force of the Government of India, on any superior officer being in the execution of his office, shall, if such assault be committed in consequence of that abetment be punished with imprisonment of either description for a term which may extend to seven years, and shall also be liable to fine S1.
The marginal note is opaque standing alone. "Such assault" is a back-reference to the assault described in section 161 S8. But the operative text does not rely on that back-reference: it spells the whole description out again, word for word. So unlike some sections in the preceding Chapter, whose marginal notes are unintelligible without their neighbours, section 162 is self-contained as an operative provision even though its heading is not S1; S8.
The elements
Five things must be established S1:
- An abetment by the accused.
- An assault -- by an officer, soldier, sailor or airman.
- That assailant must be in the Army, Navy or Air Force of the Government of India.
- The assault must be on a superior officer being in the execution of his office.
- The assault must have been committed in consequence of that abetment.
The first four are shared with section 161. The fifth is what section 162 adds S1; S8.
As with section 161, the section opens with "whoever", and only the assailant must be a member of the forces. The abettor need not be. A civilian who successfully incites a soldier to strike his commanding officer is within section 162 S1.
The causal requirement is doing real work
The words are not merely "if such assault be committed" but "if such assault be committed in consequence of that abetment" S1. An assault that happens to occur after an abetment, but independently of it, does not engage the section; the abetment must have produced it.
The Sanhita does supply a meaning for that phrase, although not in this Chapter. The Explanation to section 49 provides that an act or offence "is said to be committed in consequence of abetment, when it is committed in consequence of the instigation, or in pursuance of the conspiracy, or with the aid which constitutes the abetment" S9. That Explanation is expressed as applying to section 49 rather than to the Sanhita generally, so whether it governs the identical phrase in section 162 was not resolved for this article. The phrase is at least not left wholly without statutory guidance.
"Superior officer" is still not defined
The position recorded for section 161 is unchanged. Neither the Sanhita nor any authority located for this article says who counts as a superior officer, or whether the relationship is one of rank, of command, or of both S1; S4. The same is true of "in the execution of his office". These terms are carried forward from 1860 without definition.
The penalty, and the forum problem
The punishment is imprisonment of either description -- rigorous or simple, under section 4(c), with the choice left to the sentencing Court by section 7 -- for a term which may extend to seven years, together with liability to fine S1. No sum is expressed for the fine, so section 8(1) applies: the amount "is unlimited, but shall not be excessive" S5.
The First Schedule to the Bharatiya Nagarik Suraksha Sanhita, 2023 classifies the offence as cognizable and non-bailable, and names the trying court as a Magistrate of the first class S3.
That last column is the problem.
Seven years exceeds a first class Magistrate's power
Section 23 of the Bharatiya Nagarik Suraksha Sanhita sets out what each tier of Magistrate may impose S3:
- Section 23(1): a Chief Judicial Magistrate may pass any sentence authorised by law except death, imprisonment for life, or imprisonment exceeding seven years. No cap is placed on the fine.
- Section 23(2): a Magistrate of the first class may pass imprisonment not exceeding three years, or a fine not exceeding fifty thousand rupees, or both, or community service.
- Section 23(3): a Magistrate of the second class may pass one year, or ten thousand rupees, or both, or community service.
Section 162 carries a maximum of seven years. A Magistrate of the first class can impose three. The forum named in the First Schedule therefore cannot impose the sentence the section authorises -- it cannot impose even half of it.
This is a different limb of the problem from the one recorded at sections 157 and 161. There, the term fitted the assigned Magistrate's power and only the fine exceeded the cap. Here the imprisonment term itself is beyond the assigned forum. And seven years is not beyond every Magistrate: it sits exactly at the ceiling of a Chief Judicial Magistrate's power under section 23(1), which excludes only sentences exceeding seven years S3. So the mismatch cannot be explained away as an unavoidable consequence of trying the offence before a Magistrate at all. A Chief Judicial Magistrate could impose the full seven years. The Schedule does not name one.
This allocation is not unique to section 162
It would be wrong to present this as an isolated aberration, because the same allocation appears elsewhere in the First Schedule for offences having nothing to do with the armed forces S3:
| Section | Punishment in column 3 | Court named |
|---|---|---|
| 137(2), kidnapping | Imprisonment for 7 years and fine | Magistrate of the first class |
| 139(1), kidnapping a child for purposes of begging | Rigorous imprisonment not less than 10 years, extending to imprisonment for life, and fine | Magistrate of the first class |
| 140(3), kidnapping or abducting with intent secretly and wrongfully to confine | Imprisonment for 7 years and fine | Magistrate of the first class |
| 162 | Imprisonment for 7 years and fine | Magistrate of the first class |
Section 140(3) matches section 162 in every classification column -- seven years and fine, cognizable, non-bailable, Magistrate of the first class. Section 137(2) carries the same punishment and the same forum. And section 139(1) is a considerably larger shortfall than this one, since a sentence extending to imprisonment for life is assigned to a court that may impose three years S3.
So the entry for section 162 is one instance of a recurring allocation, not a singular drafting slip. That matters for how it should be read, and it is discussed below.
The fine is beyond reach as well
The same entry produces the other limb too. Section 162's fine is unlimited under section 8(1) S5; a first class Magistrate's fine is capped at fifty thousand rupees by section 23(2) S3. A Chief Judicial Magistrate would cure this limb as well, since section 23(1) places no cap on fine S3. The same combination is present in the kidnapping entries above, each of which couples a term beyond the assigned court's power with an unspecified and therefore unlimited fine S3; S5.
What the Code does about it
The defect is not a dead end, because the Bharatiya Nagarik Suraksha Sanhita contains a mechanism for exactly this situation.
Section 364(1) provides that whenever a Magistrate is of opinion, after hearing the evidence for the prosecution and the accused, that the accused is guilty and ought to receive a punishment "different in kind from, or more severe than, that which such Magistrate is empowered to inflict", he may record that opinion and submit his proceedings, and forward the accused, to the Chief Judicial Magistrate to whom he is subordinate. Section 364(3) then empowers that Chief Judicial Magistrate, if he thinks fit, to examine the parties, recall and examine any witness who has already given evidence, call for and take further evidence, and "pass such judgment, sentence or order in the case as he thinks fit, and is according to law" S3. The marginal note to the section is "Procedure when Magistrate cannot pass sentence sufficiently severe" S3.
So a first class Magistrate trying a section 162 case who concludes that more than three years is warranted is not powerless. He submits the case upward, and the Chief Judicial Magistrate -- who may impose up to seven years and an uncapped fine -- disposes of it.
But this is a cure with real costs, and they should be stated plainly rather than glossed over:
- It operates only at the end of the trial. The whole evidence is recorded before a forum that cannot give effect to the provision's maximum.
- The Chief Judicial Magistrate's power to re-examine parties and witnesses is discretionary ("if he thinks fit"), so whether the sentencing court hears the witnesses at all is not guaranteed by the section.
- It is triggered by the Magistrate forming an opinion that a severer sentence is due. It does not correct the allocation; it reacts to it.
This article does not assert that the First Schedule entry is legally void, and no authority was located on the effect of a Schedule entry that names a forum which cannot impose the section's maximum. Two readings are open: that the entry is an error, or that it is a deliberate allocation of ordinary cases to a first class Magistrate on the understanding that section 364 will carry the exceptional ones upward.
The recurrence of the same allocation at sections 137(2), 139(1) and 140(3) tells against the first reading. A single entry out of step with section 23 could be a slip; the same pairing of a seven-year term with a first class Magistrate, repeated across unrelated Chapters, looks more like a working assumption that Magistrates will try these offences and escalate the exceptional case under section 364 S3. That is an inference from the pattern, not a holding, and nothing located for this article decides the point. Within Chapter VIII the allocation is at least internally graded: section 161, at three years, fits a first class Magistrate exactly; section 163, at two years, goes to "Any Magistrate"; and sections 159 and 160, carrying life and death, go to a Court of Session S3.
The comparison with section 134 of the Penal Code
Section 162 replaces section 134 of the Indian Penal Code, 1860 S2. A token-level comparison, with both windows bounded before the comparison was run, returned 1.0000. There are no differences in the operative text at all. This is the fifth perfect match recorded in this collection, after sections 156, 157, 160 and 161 S1; S2.
Except in the heading, where there are now three versions
The marginal notes are not identical, and nor is the First Schedule's description S2; S1; S3:
| Document | Wording |
|---|---|
| Penal Code, section 134 | "Abetment of such assault, if the assault is committed." |
| Sanhita, section 162 | "Abetment of such assault, if assault committed." |
| First Schedule, column 2 | "Abetment of such assault, if the assault committed." |
The Sanhita's note drops both "the" and "is". The First Schedule restores "the" but not "is", producing "if the assault committed", which is ungrammatical and matches neither statute S3.
The dropping of the definite article in Sanhita marginal notes has been recorded repeatedly in this collection. What is new here is a third variant produced by the Schedule itself. Nothing turns on it legally -- a marginal note does not control the operative text, and the operative text is identical in both statutes -- but it is a drafting artefact worth recording, and it is the kind of thing that makes searching for the offence by its description unreliable.
Two amendments, across twenty-three years
Section 134 of the Penal Code carried three footnote markers, read in place from the footnote block serving the page on which the section is printed S2:
- Marker 8: substituted by Act 10 of 1927, section 2 and the First Schedule, for "or sailor" -- giving "sailor or airman".
- Marker 9: substituted by the same Act, for "or Navy" -- giving "Navy or Air Force".
- Marker 10: substituted by the Adaptation of Laws Order, 1950, for "Queen" -- giving "Government of India".
So two instruments, in 1927 and 1950, a span of twenty-three years. Both are the familiar service-reorganisation and post-Independence adaptations, and neither altered the offence's scope as between the parties.
Two cautions about that reading, both of which matter:
The footnote numbering is page-local. Marker 8 at this location is not the same amendment as marker 8 elsewhere in the Chapter. At section 132 of the Penal Code the markers 8 to 11 record a different set of amendments entirely. The markers were therefore re-read from the block serving this page rather than carried over S2.
Not every footnote in that block belongs to this section. The same block contains markers 1 to 7, which record substitutions concerning the Army Act, the Naval Discipline Act, the Indian Navy (Discipline) Act, 1934 and the Air Force Acts. Those serve section 139 of the Penal Code, which is printed on the following page. It also contains marker 11, recording the substitution by Act 26 of 1955 for "transportation for life". That does not serve section 134 either S2.
The 1955 transportation substitution does not reach this section
That last point confirms a pattern tracked across this Chapter and the preceding one. Act 26 of 1955 substituted "imprisonment for life" for "transportation for life" wherever a penalty had been expressed as transportation. Section 134's penalty was always "imprisonment of either description" for a term of years, so there was nothing for that Act to reach S2.
Section 134 is therefore the eleventh provision confirmed to fall on the negative side of that pattern: the 1955 substitution reached only penalties actually expressed as transportation, and not provisions carrying a term of ordinary imprisonment. The pattern continues to hold without exception.
The relationship between sections 161 and 162
The two sections describe the same conduct and differ only in whether the assault followed S1; S8. Section 161 punishes the abetment as such, with three years. Section 162 punishes it where the assault was committed in consequence, with seven.
This is the same grading technique used elsewhere in the Sanhita, and it raises an obvious question: if both sections cover the abetment, can an abettor whose abetment succeeded be punished under both? The only judicial statement located on these provisions addresses precisely that question, and is discussed below.
Why the general abetment provisions do not apply
A reader may wonder why the Sanhita needs sections 161 and 162 at all, given that it contains general provisions on abetment.
Section 49 provides that whoever abets any offence shall, if the act abetted is committed in consequence of the abetment, "and no express provision is made by this Sanhita for the punishment of such abetment", be punished with the punishment provided for the offence S9. That qualification is decisive. Sections 161 and 162 are express provisions for the punishment of this abetment, so section 49 is displaced and does not supply the penalty S1; S8; S9.
The same structure appears on the other side. Sections 55 and 56 deal with abetment where the offence is not committed in consequence, and both are likewise subject to the condition that no express provision is made S4. Section 161 is the express provision for that case here.
The practical effect is that this Chapter operates as a self-contained scheme for abetting an assault on a superior officer: section 161 where the assault does not follow, section 162 where it does, and the general abetment provisions standing aside in both cases.
Classification under the First Schedule
The entry, read in the full raw column layout of the First Schedule, is S3:
| Column | Entry |
|---|---|
| 1. Section | 162 |
| 2. Offence | Abetment of such assault, if the assault committed. |
| 3. Punishment | Imprisonment for 7 years and fine. |
| 4. Cognizable or not | Cognizable. |
| 5. Bailable or not | Non-bailable. |
| 6. By what Court triable | Magistrate of the first class. |
Three observations beyond the forum point already made.
The punishment column is accurate. It reads "Imprisonment for 7 years and fine", which matches the section's "shall also be liable to fine" -- liability to fine is mandatory in the sense that the Court must consider it, the section not offering imprisonment or fine as alternatives S1; S3. Some entries elsewhere in the Schedule omit a fine the section imposes. This one does not.
It is non-bailable, where section 161 is also non-bailable but section 163 is bailable. The line is drawn between assaults on superior officers and abetting desertion, rather than by length of sentence alone S3.
The description in column 2 was compared against the operative text, not only against the marginal note. That is how the third title variant was found. Comparing column 2 against the marginal note alone would have shown only that the two differ; comparing it against the operative text shows that the Schedule's description, like the marginal note, is a compressed paraphrase rather than a reproduction S1; S3.
Compounding
Section 162 is not compoundable.
Neither of the two Tables in section 359 of the Bharatiya Nagarik Suraksha Sanhita contains an entry for section 162, and the section number does not appear anywhere in either Table S3.
The word "assault" does appear in both Tables, and each occurrence was adjudicated against its own entry rather than treated as a hit on this section S3:
- Section 359(1), Table: "Assault or use of criminal force", against sections 131, 133 and 136 of the Sanhita.
- Section 359(2), Table: "Assault or criminal force in attempting wrongfully to confine a person", against section 135.
Those are the ordinary assault offences in the Chapter on offences affecting the human body. None of them is section 161 or section 162 S3.
The abetment route is closed, and this resolves an open question
Section 359(3) provides that when an offence is compoundable under that section, the abetment of such offence -- or an attempt to commit it, where the attempt is itself an offence -- "may be compounded in like manner" S3.
That provision was flagged as an open question when section 161 was examined, and it can now be closed. Section 359(3) operates on the abetment of an offence that is itself compoundable under section 359. The offence abetted here is the assault by a serviceman on his superior officer. Neither section 161 nor section 162 appears in either Table, and the assault entries that do appear are the general assault offences, not the service ones S3. There is no compoundable principal offence for section 359(3) to attach to.
The point might have been thought stronger at section 162 than at section 161, because section 162 requires the assault actually to have been committed, so there is a completed principal offence in the picture. It makes no difference. What section 359(3) requires is that the principal offence be compoundable, not that it be committed. It is not.
The duty to report does not extend to this section
Section 33(1) of the Bharatiya Nagarik Suraksha Sanhita imposes a duty on every person aware of the commission of, or of an intention to commit, an offence under one of twelve listed groups of sections, to give information to the nearest Magistrate or police officer in the absence of reasonable excuse S3.
All twelve clauses were read in full. They cover sections 103 to 105; 111 to 113; 140 to 144; 147 to 154 and 158; 178 to 182; 189 and 191; 274 to 280; 307; 309 to 312; section 316(5); 326 to 328; and 331 and 332 S3.
No section of Chapter VIII appears in any clause. Section 162 is therefore outside the statutory duty to report, as are all the Chapter's other sections. A person who knows that an assault on a superior officer is being abetted, or has been abetted and carried out, commits no offence under section 33 by staying silent. Offences against the State in the preceding Chapter attract the duty; offences relating to the armed forces do not S3.
The case law
There is one judicial statement, and -- unlike the position at section 161 -- it is about this section.
In Re: Sahadevan, decided by the Madras High Court on 23 July 1954, was a criminal revision arising out of a fatal lorry accident. The accused drove a lorry with defective brakes, lost control on a bridge, and crushed and killed an elderly pedestrian against the parapet wall. The Magistrate convicted him under section 304A of the Penal Code and under sections 116 and 121 of the Motor Vehicles Act, and imposed, in addition to the imprisonment, a fine of two hundred rupees under section 121 of that Act S6.
The question was whether that additional punishment could stand. The Court held it could not. Its reasoning was a general principle about cumulative punishment S6:
"when an unlawful act is committed and certain consequences follow from it in the usual course and the person concerned is punished in respect of such consequences, he cannot be punished over again, i.e. to say additionally for the act which produced those consequences."
The Court then gave a series of analogies. One of them is directly on this section S6:
"Under Section 132, I. P. C. a person can be punished for abetting an assault by an officer, soldier, sailor or airman on any superior officer being in the execution of his office, if such assault is committed in consequence of the abetment. But he cannot at the same time be given an additional punishment under Section 133, I. P. C. for abetment alone."
The provision the Court described -- abetting an assault on a superior officer, where the assault is committed in consequence of the abetment -- is section 134 of the Penal Code, which is now section 162 of the Sanhita. The Court cited "Section 132". Section 132 of the Penal Code concerned abetment of mutiny where the mutiny is committed, a different subject altogether S2; S6.
So the passage is a statement about the relationship between section 134 and section 133 of the Penal Code, which is to say between section 162 and section 161 of the Sanhita S1; S2; S8. Read that way, it says that an abettor punished under section 162, where the assault followed, cannot additionally be punished under section 161 for the abetment alone. The aggravated result-based provision absorbs the bare abetment provision; they operate as alternatives, not cumulatively.
Four qualifications
These matter, and the statement should not be read without them.
-
It is an analogy, not a holding. The case was about section 304A of the Penal Code and section 121 of the Motor Vehicles Act. Nothing in the disposition turned on section 134. The Court confirmed the section 304A conviction and set aside the conviction and sentence under section 121 of the Motor Vehicles Act, directing refund of the fine if realised S6.
-
The Court's first section number appears to be a slip. It cites section 132 while describing section 134. This article records that rather than silently correcting it. Notably, the Court's second number is right: section 133 of the Penal Code did punish abetment alone, so the contrast the Court drew is internally coherent and only the first citation is off S2; S6.
-
The point concerns cumulative punishment only. The passage says nothing about the ingredients of either offence, about who is a superior officer, or about what "in the execution of his office" means.
-
It is a 1954 decision of a single Judge of a High Court, on a provision of the Penal Code, applied here to a successor provision of the Sanhita. Whether an Indian court today would adopt the analogy was not researched.
Subject to all of that, this is the only judicial material located that engages the provision at all, and it is more directly on section 162 than on any other section in this Chapter.
Nothing else, and the search problems worth recording
No decision applying section 162 of the Sanhita was located. The Sanhita commenced on 1 July 2024 and reported decisions on this Chapter have not yet appeared S1.
Two search hazards are recorded for readers who may try to verify this.
A search for "section 162" is close to useless here. Section 162 of the Code of Criminal Procedure, 1973 governed the use of statements made to a police officer during investigation, and is one of the most heavily litigated provisions in Indian criminal procedure. A query for section 162 and police statements returned over ten thousand results S6. Any search for this offence must be framed by reference to section 134 of the Penal Code instead.
A distinctive phrase does work, where a general one does not. Queries built from "section 134" and from the offence description returned hundreds of results, dominated by section 134 of other enactments and by large unrelated judgments. A query built on the section's own distinctive words -- "abets an assault" together with the four service terms -- returned nine results, of which seven were statute pages (section 133 and section 134 of the Penal Code, the Penal Code itself, section 161 of the Sanhita, and the corresponding provisions of the Jammu and Kashmir State Ranbir Penal Code, 1989), one was In Re: Sahadevan, and one was an unrelated enforcement matter that does not appear to engage the provision and was not treated as authority S6. That is the whole of the located material.
Commencement and application
Section 162 commenced on 1 July 2024. Ministry of Home Affairs notification S.O. 850(E) dated 23 February 2024 appointed that date for the provisions of the Bharatiya Nyaya Sanhita, 2023, with the exception noted in that notification S7.
Conduct before 1 July 2024 falls under section 134 of the Indian Penal Code, 1860; conduct on or after that date falls under section 162 S1; S2. Because the two provisions are textually identical, the transition raises no question of altered scope -- an abettor is in exactly the same substantive position either way. The procedural position is governed by the Bharatiya Nagarik Suraksha Sanhita and its savings provisions, which were not examined for this article.
Practical points for readers
- The abettor need not be a serviceman. Only the assailant must be in the Army, Navy or Air Force of the Government of India S1.
- The distinction from section 161 is factual, not legal. Whether the charge is section 161 or section 162 turns on one question: did the assault actually occur in consequence of the abetment? S1; S8
- If it did, section 162 applies and the maximum more than doubles, from three years to seven S1; S8.
- On the located authority the two sections are alternatives, so a person punished under section 162 should not also be punished under section 161 for the same abetment -- but that rests on a 1954 analogy, not on settled law S6.
- The offence is cognizable and non-bailable, so the police may investigate without an order and bail is not a matter of right S3.
- Check the forum carefully. The First Schedule names a Magistrate of the first class, who cannot impose more than three years or a fine above fifty thousand rupees. If a severer sentence is in prospect, section 364 of the Bharatiya Nagarik Suraksha Sanhita is the route to a Chief Judicial Magistrate S3.
- The offence is not compoundable, and the abetment route in section 359(3) does not open one S3.
- There is no duty to report it under section 33 of the Bharatiya Nagarik Suraksha Sanhita S3.
- Do not search for "section 162" if you are looking for authority. Search for section 134 of the Penal Code S6.
Limitations of this article
This article is based on the sources cited and the following should be kept in view.
The forum analysis rests on reading the First Schedule entry against section 23 of the Bharatiya Nagarik Suraksha Sanhita. No authority was located on the effect of a First Schedule entry that names a court which cannot impose the section's maximum sentence, and this article does not assert that the entry is void or that a trial before a first class Magistrate would be invalid. The suggestion that the recurrence of the allocation at sections 137(2), 139(1) and 140(3) points away from simple error is an inference from the pattern, not a holding, and the comparison entries were read from the First Schedule only -- the articles on those sections were not consulted.
Section 364 was read in full, but no authority on its use was located, and nothing is asserted about how often or how readily Magistrates in fact submit proceedings under it.
Only one judicial statement on the predecessor was located, and it is an analogy offered in a case about the Motor Vehicles Act. The indication that sections 161 and 162 operate as alternatives rather than cumulatively is drawn from that analogy and is not settled law.
The Court's first section number in that analogy appears to be a slip: it cites section 132 of the Penal Code while describing section 134. This article records the slip rather than correcting it silently, and the identification of the described provision as section 134 is this article's reading of the Court's description, not something the Court itself said.
That same passage drew analogies to sections 395 and 399, and to sections 121 and 122, of the Penal Code. The latter pair are the predecessors of sections 147 and 149 of the Sanhita, which suggests that the cumulative-punishment point may bear on those sections too. Those articles were not re-examined for this one, and nothing here should be taken as a statement about them.
"Superior officer" and "in the execution of his office" are not defined in the Sanhita and no authority on their meaning was located. The scope of the fifth element, "in consequence of that abetment", is addressed by the Explanation to section 49, but whether that Explanation governs the identical phrase in section 162 was not resolved.
Sections 55 and 56 of the Sanhita were identified as the provisions dealing with abetment where the offence is not committed, but were not examined in full for this article.
The Army Act, 1950, the Indian Navy (Discipline) Act, 1934, the Air Force Act, 1950 and the Navy Act, 1957 were not examined, nor was any service law governing assaults on superior officers or the relationship between a service trial and a trial under the Sanhita. Section 1(6) of the Sanhita saves the provisions of any Act punishing mutiny and desertion of servicemen, but its interaction with this section was not researched.
The amendment history is taken from the footnote markers printed with section 134 of the Penal Code. The instruments themselves -- Act 10 of 1927 and the Adaptation of Laws Order, 1950 -- were not retrieved, and the footnote text is relied on for what they did.
No State amendment to section 162 was located, but no search of State amendment schedules was conducted, so the absence of such an amendment is not asserted as a verified fact.
No Law Commission or other legislative material explaining the retention of this section, or the choice of forum for it, was located or searched for.
The Bharatiya Nagarik Suraksha Sanhita's savings provisions governing proceedings begun before 1 July 2024 were not examined.
Sentencing practice under this section or its predecessor was not researched, and nothing is said about what sentences are in fact imposed.
Frequently asked questions
1. What does section 162 of the Bharatiya Nyaya Sanhita punish? It punishes abetting an assault by an officer, soldier, sailor or airman of the Army, Navy or Air Force of the Government of India on a superior officer who is in the execution of his office, where the assault is actually committed in consequence of that abetment S1.
2. How is it different from section 161? Only in one respect: section 162 requires that the assault actually followed from the abetment. The conduct described is otherwise identical S1; S8.
3. What is the punishment? Imprisonment of either description for a term which may extend to seven years, and the offender is also liable to fine S1.
4. How does that compare with section 161? Section 161 carries three years. Section 162 carries seven. The maximum more than doubles when the assault actually occurs S1; S8.
5. Is the fine limited? No sum is expressed, so under section 8(1) of the Sanhita the fine is unlimited but must not be excessive S5.
6. Must the abettor be a member of the armed forces? No. The section begins with "whoever". Only the assailant must be in the forces S1.
7. Does the section punish the assault itself? No. The assault is the serviceman's own offence. This section punishes the person who abetted it S1.
8. What does "such assault" in the heading mean? It refers back to the assault described in section 161. But the operative text of section 162 spells the description out in full, so the section is self-contained even though its heading is not S1; S8.
9. Which court tries it? The First Schedule names a Magistrate of the first class S3.
10. Can that Magistrate impose seven years? No. Under section 23(2) of the Bharatiya Nagarik Suraksha Sanhita a Magistrate of the first class may impose no more than three years S3.
11. Is that a defect? It is a mismatch between the punishment the section authorises and the power of the court the Schedule names. It goes further than the fine problem found at sections 157 and 161, because here the term of imprisonment itself is beyond the assigned forum. But it is not unique to this section: the Schedule makes the same allocation at sections 137(2), 139(1) and 140(3) S1; S3.
12. Could a Magistrate have imposed seven years? A Chief Judicial Magistrate could. Section 23(1) excludes only sentences exceeding seven years, and places no cap on fine. The Schedule does not name a Chief Judicial Magistrate S3.
13. So what happens if a severer sentence is warranted? Section 364 of the Bharatiya Nagarik Suraksha Sanhita applies. After hearing the evidence, a Magistrate who thinks a severer punishment is due records that opinion and submits the proceedings, forwarding the accused to the Chief Judicial Magistrate, who may then pass any lawful sentence S3.
14. Does that fix the problem? It provides a route, but only at the end of the trial, and the Chief Judicial Magistrate's power to recall witnesses is discretionary. Whether the Schedule entry is an error or a deliberate allocation relying on section 364 is not settled by anything located for this article S3.
15. Which section of the Indian Penal Code did this replace? Section 134 S2.
16. Did the wording change? No. The comparison returned a perfect match. The operative text is identical S1; S2.
17. Did the heading change? Yes, slightly. The Penal Code read "if the assault is committed"; the Sanhita reads "if assault committed"; and the First Schedule reads "if the assault committed", which matches neither S1; S2; S3.
18. Was section 134 ever amended? Twice. Act 10 of 1927 substituted "sailor or airman" and "Navy or Air Force", and the Adaptation of Laws Order, 1950 substituted "Government of India" for "Queen" S2.
19. Was it affected by the 1955 transportation amendment? No. Act 26 of 1955 reached only penalties expressed as transportation. Section 134's penalty was always imprisonment of either description for a term of years S2.
20. Is the offence cognizable and bailable? Cognizable and non-bailable S3.
21. Can the offence be compounded? No. Section 162 does not appear in either Table in section 359 of the Bharatiya Nagarik Suraksha Sanhita S3.
22. But assault offences are compoundable, aren't they? Some are. The entries mentioning assault relate to sections 131, 133, 135 and 136 of the Sanhita, which are the general assault offences. They are not the service offences in this Chapter S3.
23. Could section 359(3) make it compoundable, since the assault was actually committed? No. Section 359(3) extends compounding to the abetment of an offence that is itself compoundable under that section. The assault abetted here is not compoundable, so there is nothing for the sub-section to attach to S3.
24. Must I report this offence if I know about it? Not under section 33 of the Bharatiya Nagarik Suraksha Sanhita. No section of Chapter VIII appears in any of its twelve clauses S3.
25. Why don't the general abetment provisions apply? Section 49 applies only where no express provision is made by the Sanhita for the punishment of the abetment. Sections 161 and 162 are express provisions, so section 49 is displaced S9.
26. Is there any case law? One judicial statement was located, and it is about this provision rather than section 161: In Re: Sahadevan, Madras High Court, 23 July 1954 S6.
27. What did it say? That a person punished for abetting an assault on a superior officer where the assault was committed in consequence cannot at the same time be given an additional punishment for abetment alone. In present terms, sections 161 and 162 operate as alternatives rather than cumulatively S6.
28. Is that reliable? It must be read with care. It is an analogy in a case about the Motor Vehicles Act, from a single Judge in 1954, and the Court cited "section 132" while describing section 134. The Court's second reference, to section 133, is correct, so the contrast it drew is coherent and only the first citation is off S2; S6.
29. Has any court applied section 162 of the Sanhita? No such decision was located. The Sanhita commenced on 1 July 2024 S1.
30. Why is it hard to search for? Because section 162 of the Code of Criminal Procedure, 1973 governed the use of statements made to the police and is heavily litigated. A search for "section 162" returns over ten thousand results. Search for section 134 of the Penal Code instead S6.
31. When did section 162 come into force? On 1 July 2024, by Ministry of Home Affairs notification S.O. 850(E) dated 23 February 2024 S7.
This article states the law as published in the sources cited and is for general information only. It is not legal advice. Section 162 reproduces its predecessor word for word, but the court named in the First Schedule cannot impose the sentence the section authorises, and the only judicial statement located on the provision is a 1954 analogy whose section number appears to be a slip. Anyone facing a charge under this section, or advising on the forum in which it should be tried, should obtain professional advice on the current position before acting.