IPC2BNSConverter

BNS Section 161 · Deep dive

Section 161 BNS: Abetment of Assault by Soldier, Sailor or Airman on His Superior Officer

Section 161 of the Bharatiya Nyaya Sanhita, 2023 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 BEING IN THE EXECUTION OF HIS OFFICE. The punishment is imprisonment of either description for up to three years, and liability to fine. Its predecessor is section 133 of the Indian Penal Code, 1860, and the comparison returned 1.0000 - a PERFECT MATCH, marginal note included, the fourth in this collection after sections 156, 157 and 160. THE INDIA CODE HANDLE IS NOT CONTIGUOUS: it is 545859, not 545661. The section does not punish the assault, which is the serviceman's own offence; it punishes the abettor, WHO NEED NOT BE A SERVICEMAN - the section opens with 'whoever' and only the assailant must be in the forces. The requirement that the superior officer be 'being in the execution of his office' is a real limitation, and 'SUPERIOR OFFICER' IS NOT DEFINED: the phrase appears four times in the whole Act, in this section, in section 162 and in two Illustrations, and nowhere is it defined. THE PENALTY AND FORUM BOTH FALL SHARPLY after two sections carrying life and death: three years, tried by a MAGISTRATE OF THE FIRST CLASS - the first Magistrate forum in Chapter VIII. AND THAT CREATES A FORUM PROBLEM, the SECOND INSTANCE IN THIS COLLECTION after section 157 and structurally identical to it: the three-year maximum fits section 23(2) of the Bharatiya Nagarik Suraksha Sanhita, 2023 exactly, but the section names no sum for the fine, so section 8(1) of the Sanhita makes it UNLIMITED while that court may impose no more than fifty thousand rupees. IT NARROWS for the same reason as before - a Chief Judicial Magistrate is also a Magistrate of the first class and section 23(1) imposes no fine cap - so the practical significance is modest. Section 133 carried THREE amendments, not four: the air force additions of 1927 and the 1950 Crown adaptation, but NO 1955 transportation substitution, because the section never carried transportation - the same reasoning that explained section 129's blank history. On the First Schedule the REVERSE DIVERGENCE FOUND AT SECTION 159 RECURS AND IS NOW A PATTERN: the Schedule's description includes 'an officer', which the section's own MARGINAL NOTE OMITS though the operative text contains it, so the Schedule is again the more faithful of the two - two of two in this Chapter - and the deficiency is inherited. The punishment column renders 'liable to' as 'and' for the ninth time, but the fine-attachment defect does NOT arise, because this entry has a single sentencing limb; that was checked rather than assumed. The offence is cognizable, non-bailable and not compoundable, though the compounding probe needed care because assault offences ARE compoundable - the entries are sections 131, 133, 135 and 136 of the Sanhita, and a NUMBER TRAP is recorded: Sanhita section 133 is a compoundable assault offence while Penal Code section 133 is this section's predecessor, and they have nothing to do with each other. An open question is also recorded and expressly not answered: whether section 359(3), which extends compounding to the abetment of a compoundable offence, could reach a charge under section 161 where the assault abetted is itself compoundable. ON CASE LAW, one judicial statement on the predecessor was located - In Re: Sahadevan, Madras High Court, 23 July 1954 - and it comes with THREE QUALIFICATIONS: it is an ANALOGY in a case about the Motor Vehicles Act and not a decision on the section; the Court cited 'Section 132, I.P.C.' while describing section 134; and the point concerns cumulative punishment only. Subject to those, it indicates that where the assault is actually committed the abettor is punished under the result-based provision, now section 162, and should NOT also be punished under this section for the abetment alone - so the two operate as alternatives. That is offered as an indication and not as settled law.

By the Nyaya Yantra Editorial TeamLaw checked as of 16 October 2026 29 min read

Prepared with AI-assisted research from the official sources listed at the end of this article.

At a glance

Provision
BNS Section 161 — Abetment of assault by soldier, sailor or airman on his superior officer, when in execution of his office
Earlier law (IPC)
Indian Penal Code, 1860, s. 133 · direct
Side-by-side converterIPC 133 → BNS 161

The provision in one view

Section 161 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. The punishment is imprisonment of either description for a term which may extend to three years, and the offender is also liable to fine S1; S4.

Its predecessor is section 133 of the Indian Penal Code, 1860 S2. The comparison returned 1.0000 -- a perfect match, operative text and marginal note alike.

Five findings:

  • The penalty and the forum both fall sharply. After two sections carrying life and death, this one carries three years and is tried by a Magistrate -- the first in Chapter VIII.
  • And that creates a forum problem, because the section's fine is unlimited while a Magistrate's is capped. This is the second instance of that defect in this collection.
  • "Superior officer" is not defined, and neither the Sanhita nor any located authority says who counts as one.
  • There is, for the first time in this Chapter, a judicial statement on the predecessor -- though it is an analogy offered in a case about the Motor Vehicles Act, and the Court's companion section number appears to be a slip.
  • The handle for this section is not contiguous. It is 545859, not 545661.

The exact words

"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 be punished with imprisonment of either description for a term which may extend to three years, and shall also be liable to fine." S1; S4

The elements

Four things must be established S1:

Element
1an assault
2by an officer, soldier, sailor or airman in the Army, Navy or Air Force of the Government of India
3on a superior officer
4that superior officer being in the execution of his office

and the accused must have abetted it.

Note what the section does not punish. It does not punish the assault -- that is the serviceman's own offence. It punishes the outsider, or the fellow serviceman, who abets it. The abettor need not be a member of the forces himself: the section opens with "whoever", and only the assailant must be a serviceman.

The fourth element is a real limitation. The superior officer must be "being in the execution of his office" at the time. An assault on a superior officer off duty would not fall within this section, though it might be an offence elsewhere. What "in the execution of his office" requires was not researched, and no authority on it was located.

"Superior officer" is not defined, and the phrase is rare

The expression appears four times in the whole Sanhita S4:

  • in this section;
  • in section 162, the result-based counterpart;
  • in an Illustration to a general exception, concerning a soldier who fires on a mob by the order of his superior officer;
  • in an Illustration to the defamation provisions, concerning a Magistrate making a report to his superior officer.

So the only operative uses are sections 161 and 162, and neither defines it. Whether seniority is a matter of rank, of appointment, of command in the particular situation, or of something else is not addressed by the Sanhita and no authority was located.

The four service terms are undefined too. This collection's work on section 159 established that the Penal Code's Explanation defining "officer", "soldier", "sailor" and "airman" has been dropped, and that it never applied beyond section 131 in any event S2.

A note on how that was checked

A search of the Gazette for the phrase "execution of his office" returns no occurrences at all S4. That is a false result, and the section plainly contains the phrase.

The cause is the Gazette's two-column layout: the marginal note is interleaved into the operative text, so the printed sequence reads "...being in the execution assault by of his office...". A search for the phrase therefore fails even though the phrase is there.

The section's text was taken from the official section record, where it is intact S1. This is the third time in this collection that marginal-note interleaving has produced a false negative in the Gazette, after sections 152 and 156. The reliable probe is the shorter fragment "in the execution", which returns three occurrences.

The penalty, and a forum problem

The punishment is imprisonment of either description for up to three years, and the offender "shall also be liable to fine" S1.

Two points follow.

It is "either description", so the court chooses between rigorous and simple imprisonment. Section 157 remains the only section examined in this collection that requires simple imprisonment.

And the section names no sum for the fine. Section 8(1) of the Sanhita supplies the consequence:

"Where no sum is expressed to which a fine may extend, the amount of fine to which the offender is liable is unlimited, but shall not be excessive." S5

The Magistrate cannot impose that fine

The First Schedule assigns the offence to a Magistrate of the first class S3. Section 23(2) of the Bharatiya Nagarik Suraksha Sanhita, 2023 provides that such a court

"may pass a sentence of imprisonment for a term not exceeding three years, or of fine not exceeding fifty thousand rupees, or of both, or of community service." S3

The imprisonment fits exactly. Three years does not exceed three years.

The fine does not. The section permits an unlimited fine; the court may impose no more than fifty thousand rupees.

This is the second instance of that defect in this collection, after section 157 -- and the two are structurally identical: a three-year maximum that fits the Magistrate's powers precisely, coupled with an uncapped fine that does not.

And it narrows, for the same reason

"Magistrate of the first class" includes a Chief Judicial Magistrate, and section 23(1) gives that court "any sentence authorised by law except a sentence of death or of imprisonment for life or of imprisonment for a term exceeding seven years" -- which contains no cap on fine at all S3.

So the limitation bites only where an ordinary first-class Magistrate tries the case. As at section 157, the practical significance is modest, and this article does not suggest otherwise. No authority on the point was located, and whether a court faced with a case calling for a larger fine would commit it elsewhere or simply impose the capped fine was not researched.

The comparison with section 133 of the Penal Code

The Penal Code provision read:

"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 be punished with imprisonment of either description for a term which may extend to three years, and shall also be liable to fine." S2

A token-level comparison, with both windows bounded before any comparison was run, returned 1.0000. There are no differences at all, and the marginal notes are identical S1; S2.

This is the fourth perfect match in this collection, after sections 156, 157 and 160.

Section 133 carried no Explanation, consistent with this collection's finding that Chapter VII of the Penal Code contained exactly one, in section 131 S2.

Three amendments, not four

Three footnote markers serve the section 133 block, and they were re-read in place from the footnote block serving that printed page rather than carried over from the neighbouring sections S2:

MarkerRecords
8"sailor or airman" substituted for "or sailor" by Act 10 of 1927, section 2 and the First Schedule
9"Navy or Air Force" substituted for "or Navy" by the same Act and Schedule
10"Government of India" substituted for "Queen" by the Adaptation of Laws Order, 1950

There is no fourth marker, and its absence is explained by the section's own penalty. Section 132 carried a marker recording the conversion of "transportation for life" into "imprisonment for life" by Act 26 of 1955. This section never carried transportation: its maximum has always been three years' imprisonment, so the 1955 Act had nothing to substitute.

That is the same reasoning that explained the blank amendment history of section 129, examined in this collection at section 157. The pattern is that the 1955 substitution reached only those provisions whose penalties were expressed in terms of transportation.

As always this rests on the footnote apparatus published with the Penal Code. The 1860 Gazette has not been retrieved, and the absence of a marker is evidence of no recorded amendment rather than proof that none occurred.

Classification under the First Schedule

The First Schedule classifies the offence as follows S3:

ColumnEntry
OffenceAbetment of assault by an officer, soldier, sailor or airman on his superior officer, when in execution of his office
PunishmentImprisonment for 3 years and fine
Cognizable or non-cognizableCognizable
Bailable or non-bailableNon-bailable
By what court triableMagistrate of the first class

The first Magistrate forum in Chapter VIII

Sections 159 and 160 are both tried by a Court of Session, as of necessity -- their maxima of life and death are beyond every Magistrate's powers. Section 161 is the first section of this Chapter assigned to a Magistrate S3.

That is recorded as a structural observation, not as a view on whether the assignment is appropriate -- subject to the fine problem described above.

The reverse divergence recurs, and is now a pattern

As at section 159, the Schedule's description is more complete than the Sanhita's own marginal note S1; S3:

text
operative text"abets an assault by an officer, soldier, sailor or airman"
marginal note"Abetment of assault by soldier, sailor or airman"
Schedule"Abetment of assault by an officer, soldier, sailor or airman"

The marginal note omits "officer". On the label alone a reader would not know that abetting an assault committed by an officer is covered -- and the operative text plainly covers it.

The Schedule restores the word, and so matches the section.

This is the second such divergence in Chapter VIII, after section 159, where the marginal note omitted both "officer" and "allegiance". Two of two. In this Chapter, so far, the marginal notes drop "officer" and the Schedule puts it back.

And the deficiency is inherited: the Penal Code's marginal note to section 133 is identical S2.

The punishment column, once

"Liable to" has become "and" S1; S3. The section says the offender "shall also be liable to fine"; the Schedule says "and fine". This is the ninth instance of that defect in this collection, after sections 153 to 160.

The second Schedule defect found at sections 156, 158, 159 and 160 does not arise here. Those entries had two or three sentencing limbs, and the fine appeared attached to the last of them. This entry has a single limb, so there is no other sentence for a fine to be excluded from. That was checked rather than assumed.

As elsewhere, nothing turns on the wording as a matter of law: the First Schedule classifies offences for procedural purposes and does not define the punishment, which is fixed by section 161.

Compounding

Section 161 appears in neither table of compoundable offences in section 359 of that Sanhita. The offence is not compoundable S3.

A probe for "161" was negative in both tables. Probes for "assault" produced hits in both, and this needed care, because assault offences are compoundable. Each was checked against its own entry S3:

  • in the first table, "Assault or use of criminal force" is listed against sections 131, 133 and 136, compoundable by the person assaulted or against whom criminal force is used;
  • in the second, "Assault or criminal force in attempting wrongfully to confine a person" is listed against section 135, compoundable by the person assaulted.

So the compoundable assault offences are sections 131, 133, 135 and 136 of the Sanhita -- not section 161.

A number trap worth recording

One of those compoundable entries is section 133 of the Sanhita -- and section 133 of the Penal Code is the predecessor of this section S2; S3.

The two have nothing to do with each other. Sanhita section 133 is an assault offence; Penal Code section 133 is abetment of a service assault. A probe of the compounding tables for "133", run in the expectation of finding the predecessor, would have returned a hit for an entirely different provision. The numbers coincide and the subject matter does not.

An open question on abetment

Section 359(3) provides that where an offence is compoundable under that section, the abetment of such an offence may also be compounded S3.

The assault abetted under section 161 may itself be a compoundable offence -- an assault under section 131, for instance. Whether section 359(3) therefore reaches a charge under section 161 is a question this article does not answer. Section 161 is a distinct offence appearing in neither table, and section 359(3) speaks of the abetment of a compoundable offence rather than of a separately constituted abetment offence. The point was not researched and no authority on it was located. It is recorded because it is arguable, not because it is resolved.

The duty to report does not extend to this section

All twelve clauses of section 33(1) of the Bharatiya Nagarik Suraksha Sanhita, 2023 were read when this collection examined section 159, and no section of Chapter VIII appears in any of them S3. Section 161 is therefore outside the duty to report.

The case law

One judicial statement on the predecessor was located, and it requires three qualifications.

In In Re: Sahadevan, decided by the Madras High Court on 23 July 1954, the accused drove a lorry whose brakes had effectively failed, could not stop at a bridge, swerved, and crushed an elderly pedestrian against the parapet, killing him. He was convicted under section 304A of the Penal Code and under sections 116 and 121 of the Motor Vehicles Act S6.

The question was whether the additional sentence under section 121 of that Act -- driving with a defect the driver knew of -- could stand alongside the conviction for causing death by a rash or negligent act. The Court held that it could not, reasoning 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."

To illustrate that principle the Court gave a series of analogies, and one of them is 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 Court's other analogies were murder against grievous hurt; dacoity under section 395 against preparation under section 399; waging war under section 121 against preparation under section 122; and abetment under section 109 against abetment under section 116 S6.

The conviction under section 304A was confirmed and the conviction and sentence under section 121 of the Motor Vehicles Act were set aside, with the fine to be refunded S6.

The three qualifications

First, this is an analogy, not a decision on the section. The case concerned the Motor Vehicles Act. What the Court said about sections 132 and 133 is illustrative reasoning and not a ruling on either, and it is used here as such.

Second, the Court's section number appears to be a slip. The provision it describes -- abetting an assault on a superior officer where the assault is committed in consequence -- is section 134 of the Penal Code, the predecessor of section 162 of the Sanhita. Section 132 of the Penal Code concerned abetment of mutiny, not assault. This article does not correct the Court; it records the discrepancy and relies on the description, which is unambiguous, rather than on the number.

Third, the point itself is about cumulative punishment, not about what either section requires. It says nothing about who is a "superior officer", what "in the execution of his office" means, or what abetment requires.

Subject to those three points, what the passage indicates is this: where the assault is actually committed in consequence of the abetment, the abettor is punished under the result-based provision -- now section 162 -- and should not also be punished under this section for the abetment alone. On that reading sections 161 and 162 operate as alternatives rather than cumulatively, which is consistent with the structure this collection found at sections 159 and 160. It is offered as an indication and not as settled law.

Nothing else, and two search problems

No other authority on section 133 or section 161 was located.

A search on section 133 of the Penal Code returned twelve results, of which this was the only one engaging the section. The rest were the section text, procedural codes of 1898 and 1989, the Jammu and Kashmir State Ranbir Penal Code, 1989, criminal rules of 1977, and judgments turning on section 133 of the Code of Criminal Procedure -- the power to make a conditional order for removal of a public nuisance S2.

A search on section 161 of the Sanhita returned nine results, and the collision this collection anticipated is present and severe: section 161 of the Code of Criminal Procedure, 1973 governs police examination of witnesses and is among the most frequently cited provisions in Indian criminal law. The results were statute texts and judgments concerning that provision S1.

A query built on this section's supposedly distinctive terms failed badly, returning 231 results headed by police regulations, a prohibition statute and major constitutional decisions S2. The terms are not distinctive at all: "superior officer" and "execution of his office" are common in Indian statutes and judgments. That is reported as a query-design failure rather than as a finding about the section.

The judgments already held for this collection were searched, using a pattern that tolerates a line break inside the citation. Their references to "section 133" all concern section 133 of the Indian Evidence Act, 1872 -- accomplice evidence -- or section 133 of the Motor Vehicles Act, and their references to "superior officer" are incidental S2.

Commencement and application

Section 161 came into force on 1 July 2024, by Ministry of Home Affairs notification S.O. 850(E) dated 23 February 2024 S7.

Conduct before that date falls under section 133 of the Penal Code; conduct on or after it falls under section 161 S1; S2. Since the two provisions are textually identical, the transition raises no question of altered scope.

Practical points for readers

  • The abettor need not be a serviceman. The section says "whoever"; only the assailant must be S1.
  • The section punishes abetting the assault, not committing it S1.
  • The superior officer must be in the execution of his office at the time. What that requires was not researched S1.
  • "Superior officer" is not defined anywhere in the Sanhita, and the phrase has only one other operative use, in section 162 S4.
  • The four service terms are undefined too, the Penal Code's definition having been dropped S2.
  • Three years' imprisonment, of either description, and liability to fine S1.
  • The fine is unlimited by the section, because no sum is expressed S1; S5.
  • But a Magistrate of the first class cannot impose more than fifty thousand rupees S3.
  • This is the first offence in Chapter VIII tried by a Magistrate S3.
  • Cognizable, non-bailable, not compoundable S3.
  • Failing to report this offence is not itself an offence under section 33 of the Bharatiya Nagarik Suraksha Sanhita, 2023 S3.
  • Where the assault is actually committed, section 162 applies, and a 1954 analogy indicates the two should not both be punished -- though that is not settled law S6.

Limitations of this article

  • Only one judicial statement on section 133 of the Indian Penal Code, 1860 was located, and it is an analogy in a case about the Motor Vehicles Act. It is not a decision on the section. No authority on section 161 of the Sanhita was located at all.
  • The Court's 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 discrepancy and relies on the description rather than the number; it does not assert that the Court erred, and the point was not researched further.
  • The indication that sections 161 and 162 operate as alternatives rather than cumulatively is drawn from that analogy and is not settled law. No decision on the relationship between the two sections was located.
  • That analogy also touched sections 121 and 122 of the Penal Code, the predecessors of sections 147 and 149 of the Sanhita, suggesting that a person punished for waging war should not additionally be punished for preparing to wage war. This article does not pursue that, which belongs to those sections; it is recorded so the point is not lost.
  • "Superior officer" is not defined in the Sanhita and no authority construing it was located. Whether seniority turns on rank, appointment, command in the situation or something else is not addressed.
  • "In the execution of his office" was not researched and no authority on it was located.
  • The four service terms are undefined. The effect of the Penal Code Explanation's deletion is discussed in this collection's article on section 159 and is not reopened here.
  • The Sanhita's general provisions on abetment and on assault were not examined, so what the abetment element requires, and what constitutes the assault abetted, are outside this article.
  • Whether section 359(3) of the Bharatiya Nagarik Suraksha Sanhita, 2023 makes a charge under section 161 compoundable, on the footing that the assault abetted is itself compoundable, was not researched. The question is recorded as arguable and is not answered.
  • The forum analysis rests on the three provisions quoted -- section 161, section 8(1) of the Sanhita and section 23 of the Bharatiya Nagarik Suraksha Sanhita. No authority on the mismatch was located.
  • Section 162 was not analysed beyond noting its subject matter and its place in the pair.
  • Act 10 of 1927 was not retrieved. Its effect on this section is recorded from the footnote apparatus published with the Penal Code.
  • The Gazette of 1860 has not been retrieved.
  • No Law Commission report or legislative-committee material was located or searched for this section.
  • A Gazette search for "execution of his office" returns nothing, because the marginal note is interleaved into the operative text in the printed two-column layout. The section's wording is taken from the official section record. This is disclosed because a reader repeating the search would get a misleading result.
  • The First Schedule's rendering of "liable to" as "and" is reported as a defect in the Schedule. No authority was located on what a court should do where the Schedule and the section conflict.
  • Bail law was not examined beyond recording the Schedule's classification.
  • Community service, which section 23(2) also permits a first-class Magistrate to order, was not examined in relation to this offence.

Frequently asked questions

1. What does section 161 of the Bharatiya Nyaya Sanhita punish? 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 S1.

2. Must the abettor be a member of the armed forces? No. The section says "whoever". Only the person who commits the assault must be a serviceman S1.

3. Does the section punish the assault itself? No. It punishes abetting it. The assault is the serviceman's own offence S1.

4. What if the superior officer was off duty? The section requires him to be "being in the execution of his office". What that requires was not researched and no authority was located S1.

5. Who is a "superior officer"? The Sanhita does not say. The phrase appears four times in the Act and is never defined; its only other operative use is in section 162 S4.

6. What is the punishment? Imprisonment of either description for up to three years, and the offender is also liable to fine S1.

7. Is the fine limited? Not by the section, which names no sum. Section 8(1) of the Sanhita makes such a fine unlimited, though it must not be excessive S1; S5.

8. So can the Magistrate impose an unlimited fine? No. Section 23(2) of the Bharatiya Nagarik Suraksha Sanhita, 2023 caps a first-class Magistrate's fine at fifty thousand rupees S3.

9. Is that a problem? It is a mismatch, and the second of its kind in this collection after section 157. It narrows considerably, because a Chief Judicial Magistrate is also a Magistrate of the first class and section 23(1) imposes no fine cap on that court S3.

10. Which court tries it? A Magistrate of the first class -- the first section in Chapter VIII not assigned to a Court of Session S3.

11. Which section of the Indian Penal Code did this replace? Section 133 S2.

12. Did the wording change? No. The comparison returned 1.0000 -- a perfect match, marginal note included S1; S2.

13. Was section 133 ever amended? Three times on the footnotes: the air force was added by Act 10 of 1927 in two places, and "Queen" became "Government of India" by the Adaptation of Laws Order, 1950 S2.

14. Why no 1955 amendment, when section 132 had one? Because that Act replaced "transportation", and this section never carried it -- its maximum has always been three years' imprisonment S2.

15. Does the First Schedule describe the offence correctly? Better than the marginal note does. The Schedule includes "an officer", which the marginal note omits though the operative text contains it. Its punishment column says "and fine" where the section says "liable to" S1; S3.

16. Can the offence be compounded? No. Section 161 appears in neither table in section 359 of that Sanhita S3.

17. But assault offences are compoundable, aren't they? Some are -- sections 131, 133, 135 and 136 of the Sanhita. None of those is section 161 S3.

18. Could section 359(3) make it compoundable, since the assault abetted may be? That is arguable and this article does not answer it. Section 161 is a distinct offence in neither table, and the question was not researched S3.

19. Must I report this offence if I know about it? No. All twelve clauses of section 33(1) of that Sanhita were read and no section of Chapter VIII appears in any of them S3.

20. Is there any case law? One judicial statement on the predecessor was located, in a 1954 Madras decision about the Motor Vehicles Act. It mentions the section only by way of analogy S6.

21. What did it say? That a person punished for abetting such an assault where the assault was actually committed cannot also be punished for the abetment alone. It is illustrative reasoning, not a ruling on the section S6.

22. Is that reliable? It should be treated with care. It is an analogy in an unrelated case, and the Court cited section 132 of the Penal Code while describing section 134 S6.

23. Does searching for "section 161" produce misleading results? Yes, badly. Section 161 of the Code of Criminal Procedure, 1973 governs police examination of witnesses and is one of the most cited provisions in Indian criminal law S1.

24. When did section 161 come into force? 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 161 reproduces its predecessor word for word; the penalty and forum fall sharply from the two preceding sections, and the fine the section permits is unlimited while the Magistrate it is assigned to may impose no more than fifty thousand rupees; "superior officer" and "in the execution of his office" are both undefined and unconstrued; and the only judicial statement located on the predecessor is an analogy in a case about the Motor Vehicles Act, in which the Court's companion section number appears to be a slip. Anyone affected by, or advising on, a matter under this section should obtain qualified legal advice. Verify the current text, and take advice on your own facts, before acting.

Sources

  1. S1The Bharatiya Nyaya Sanhita, 2023 - Section 161 — India Code, Legislative Department, Ministry of Law and Justice (accessed 16 October 2026)
  2. S2The Indian Penal Code, 1860 - Sections 133 and 134 — India Code, Legislative Department, Ministry of Law and Justice (accessed 16 October 2026)
  3. S3The Bharatiya Nagarik Suraksha Sanhita, 2023 - Sections 23, 33 and 359 and the First Schedule — Ministry of Home Affairs, Government of India (accessed 16 October 2026)
  4. S4The Bharatiya Nyaya Sanhita, 2023 - Gazette of India Extraordinary — Ministry of Home Affairs, Government of India (accessed 16 October 2026)
  5. S5The Bharatiya Nyaya Sanhita, 2023 - Section 8 — India Code, Legislative Department, Ministry of Law and Justice (accessed 16 October 2026)
  6. S6In Re: Sahadevan — Madras High Court (text via Indian Kanoon) (accessed 16 October 2026)
  7. S7Ministry of Home Affairs notification S.O. 850(E) dated 23 February 2024 — Ministry of Home Affairs, Government of India (accessed 16 October 2026)

Related deep dives

← All BNS section deep dives