The Supreme Court’s treatment of PW12 (the approver) in State of Tamil Nadu v. Ponnusamy & Ors. dated May 19, 2026, citation: 2026 INSC 507 substantially refines how trial courts should appreciate approver evidence in a modern conspiracy-cum-murder trial. The judgment both re‑affirms the classic prudential rule of corroboration and corrects some recurring mistakes in how contradictions and “improvements” in an approver’s version are evaluated.
1. The starting point: approver evidence is usable, but with prudence
The Court begins from the settled position that an approver’s testimony is not inherently inadmissible; rather, it is a species of accomplice evidence which must be approached with caution and accepted only when there is sufficient independent corroboration in material particulars. It expressly states that PW12’s evidence cannot be discarded merely because he is an approver; instead, it must be tested on reliability and corroboration like any other accomplice, applying the rule of prudence articulated in earlier authorities such as Sarwan Singh v. State of Punjab.
Crucially, the Court emphasizes that in this case the conviction is not resting solely on the approver’s word. PW12’s account of the conspiracy, timelines, roles, money flow and the execution of the murder is “specific in nature” and is independently backed by public witnesses (PW2, PW3, PW4, PW5, PW53), the money trail and other circumstantial links. The Court repeatedly stresses that the approver has only made the chain more “consistent and wholesome”; the prosecution’s structure is not standing on him alone.
Practice point: For a Sessions Court, the first question is not “approver yes or no”, but “approver plus what?” If the rest of the record is thin and speculative, an approver cannot rescue it; if there is a reasonably strong independent chain, an approver can legitimately be used to cement and explain it.
2. Legality of pardon and the error of importing “bias”
The High Court had tried to inject an additional layer of distrust towards PW12 based on an administrative letter by the original Sessions Judge who granted pardon, expressing a possible conflict and seeking transfer of the case. Treating that letter (taken on record as Ex. C6) as indicative of “reasonable apprehension of bias”, the High Court concluded that the very process of grant of pardon was suspect and that PW12’s testimony must therefore be viewed with extra suspicion.
The Supreme Court finds this approach fundamentally flawed. It points out that:
The Judge herself voluntarily disclosed the potential conflict at the earliest and sought transfer, which in fact reflects fairness rather than bias.
That Judge did not conduct the trial or record PW12’s evidence; the successor Judge did.
The High Court took the administrative letter as additional evidence at the appellate stage in an irregular manner, without following Section 294 CrPC and without affording the prosecution or the Judge any opportunity to respond.
On this reasoning, the Court holds that the apprehension of bias was ill‑founded and that no extra penal standard could be superimposed on the approver’s evidence on that basis.
Practice point: When faced with a challenge to the pardon itself, a trial judge should check: (i) statutory compliance (Sections 306/307 CrPC), (ii) voluntariness and completeness of disclosure, and (iii) absence of obvious mala fides; speculative narratives about judicial bias should not be allowed to contaminate the evidentiary evaluation of the approver’s testimony.
3. The core insight: the “character” of the maker has changed
The single most important doctrinal move of the judgment is the way it deals with contradictions between PW12’s earlier statement under Section 161 CrPC (when he was Accused A10) and his later deposition after becoming an approver. The High Court treated the omissions and improvements between the two as fatal, showing that PW12 was unreliable.
The Supreme Court accepts that there are contradictions and omissions, but says two things that are critical for trial practice:
At the 161 stage, PW12 was being examined as an accused, not as a witness, and was naturally inclined to conceal his role and minimise self-incrimination.
After grant of pardon, he took the witness stand under oath with an obligation to make a “true and full disclosure”, now free (in relative terms) from the fear of self-incrimination.
The Court therefore explains that the “character” of the person making the statements has changed: from a self‑protective accused under Section 161 to a pardoned accomplice under oath. In that setting:
The very object of pardon is to elicit a fuller, more incriminating narrative than what the person had previously admitted as an accused.
If an approver’s post‑pardon, fuller statement is rejected only because it contradicts his earlier, self‑serving version, the very purpose of pardon is defeated.
The phrase “true and full disclosure” inherently presupposes that earlier disclosures were neither wholly true nor complete.
Accordingly, the Court holds that contradictions between the 161 statement and the later deposition do not automatically demolish the approver; their weight must be judged contextually, keeping in view the changed position of the witness and the corroborative backdrop.
Practice point: When defence puts 161‑based contradictions to an approver, the trial judge should (i) allow them under Sections 161/162, (ii) record them properly, but (iii) in the judgment, evaluate their significance in the light of the witness’s changed legal position and corroboration. A mere “improvement” is not fatal if it is a natural consequence of a shift from concealment to full disclosure and is backed by independent evidence.
4. Use of the earlier 161 statement: “yes, but…”
The Court clarifies an important technical point: a non‑confessional statement of an accused recorded during investigation qualifies as a Section 161 statement and may be used for contradiction if that person later enters the witness box, including as an approver. The bar under Section 162 CrPC does not prevent such use for contradiction, though confessional portions remain barred under Section 25 of the Evidence Act except to the limited extent permitted by Section 27.
However, the Court immediately adds two qualifiers of direct practical relevance:
The weight of such contradictions must be assessed case by case. A contradiction that merely reflects fuller disclosure after pardon is not equivalent to a contradiction suggesting deliberate fabrication.
Only non‑confessional, admissible portions can be used for contradiction; confessional portions cannot be pressed into service indirectly through Section 162.
Practice point: In the judgment, a Sessions Judge should explicitly distinguish (a) what contradictions were proved from the 161 statement, and (b) why particular contradictions matter (or do not matter), instead of treating all contradictions as of equal gravity.
5. Corroboration: what kind, and how much?
The Court re‑affirms the “twin tests” for approver evidence: intrinsic reliability and external corroboration in material particulars. It emphasises that in this case PW12’s narrative is not an isolated story; it is “wholly consistent with the other direct and circumstantial evidence on record.”
Examples of corroboration identified by the Court include:
PW4 and PW5 (real estate brokers) confirming the second conspiracy meeting, presence of the main conspirators, and the express statement that “doctor will be no more” when the disputed land board was discussed.
PW53 independently narrating the first conspiracy meeting at A5’s house, the discussion about eliminating Dr. Subbiah, the role of A1–A3, A5, A7–A9, and even the decision not to kill the doctor at his house after reconnaissance.
PW2 and PW3 as direct witnesses to the attack, corroborating the presence and conduct of the assailants, including PW12’s role at the scene (keeping watch and the bike ready for escape), thereby tying him to the actual murder and not merely to earlier meetings.
The money trail (bank transfers from A1/A3/A5, withdrawal and cash distribution through A6 and DW2) which lines up with the conspiracy timeline narrated by PW12.
The Court notes that different witnesses, with no close linkage to each other, are deposing to overlapping segments of the same chain, thereby mutually reinforcing PW12 on key aspects such as participants, dates, locations, roles, and motive.
Practice point: The “material particular” that must be corroborated is not every minor detail; it is the essential incriminating elements—identity of co‑accused, their role in the conspiracy, link to the actus reus, and the flow of consideration. Corroboration can be by circumstances, conduct, documents, or neutral witnesses; it need not be direct ocular evidence of every overt act.
6. Dealing with delay, omissions, and “tailoring” allegations
The High Court had attacked the approver partly on the basis that his later testimony appeared to match the prosecution theory and other witnesses, suggesting tutoring and tailoring. The Supreme Court counters this by looking at the broader pattern: PW12 disclosed details that were either previously unknown to the police (such as specific lodges and timings in Chennai) or could only be verified after his disclosure; several of these were in fact corroborated by independent evidence.
The Court reiterates its general position that not every contradiction or omission is fatal; each must be weighed “in light of the surrounding evidence and the peculiar facts associated with a witness.” In the context of an approver, some omissions at the accused stage are natural, and some later additions may be natural reflections of the obligation to tell the whole truth after pardon.
Practice point: In conspiracy cases, it is unrealistic to expect initial police statements to contain a perfectly coherent, fully self‑incriminating narrative from a participant. A trial court should be more suspicious of contradictions that go to the core of the prosecution story (e.g., a completely different set of conspirators) than of those which merely add detail (dates, sums, places) consistent with an already proved framework.
7. A practical framework for trial courts and counsel
Drawing from the reasoning in this judgment, a practical framework for appreciating approver evidence may be stated as follows:
Check the pardon: Ensure compliance with Sections 306/307 CrPC, voluntariness, and that the approver understood the obligation of “true and full disclosure”; record it briefly in the judgment.
Assess intrinsic reliability: Is the narrative internally consistent, detailed in a way that suggests first‑hand knowledge, and free from glaring improbabilities?
Map corroboration: For each major incriminating assertion (who, where, when, how, for how much), identify independent support—other witnesses, documents, call records, money trail, recoveries, medical or forensic evidence.
Handle 161 contradictions carefully: Allow them to be proved, but in the reasoning distinguish “natural fuller disclosure post‑pardon” from contradictions that suggest deliberate shifting of blame or invention.
Avoid circular corroboration: PW12 cannot be used to corroborate PW4/PW5 and then PW4/PW5 used to “corroborate” PW12 on the same bare point; at least one strand must be independently rooted in objective circumstance or a neutral source.
Write reasons explicitly: Instead of a generic line (“approver evidence corroborated”), identify 2–3 specific segments where the approver is supported, and 1–2 segments where caution leads the court to ignore his uncorroborated assertions.
This is, in effect, what the Supreme Court does with PW12: it accepts his evidence where the record independently supports him and declines to make the case rest on him where the record is thin.
8. Why this judgment matters for approver jurisprudence
The judgment is important for day‑to‑day trial work because it resists two opposite errors: the High Court’s tendency to treat any deviation from the 161 statement as fatal, and the traditional temptation in some trial courts to treat an approver as a “star witness” once pardon is granted. It restores the classical middle path: an approver is neither unusable nor automatically safe; he is a potentially valuable but structurally suspect witness whose word must be meticulously cross‑checked against the totality of evidence.
For judges and the legal fraternity, the key takeaway is that approver evidence is a tool of clarification, not a shortcut to conviction. After Ponnusamy, the law expects trial courts to recognise the change in the approver’s position, to use 161 contradictions intelligently rather than mechanically, and to insist on real, external corroboration of the incriminating heart of his story.
No comments:
Post a Comment