Fill in the following details to e-mail
To
Cc
Subject
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> </head> <body> <div style="font-family:Verdana, Geneva, sans-serif; font-size:12px; text-align:justify"> <table width="800" border="0" style="border:1px solid #ccc;padding:5px;" align="center" cellpadding="6" cellspacing="0"> <tr> <td align="left" valign="top"> <br /> Supreme Court <br /><br /> A breach of a promise cannot be said to be a false promise<br /><br /> MANU/SC/1142/2019 - (21 Aug 2019)<br /><br /> </td> </tr> <tr> <td align="left" valign="top">Pramod Suryabhan Pawar Vs. The State of Maharashtra and Ors.</td> </tr> <tr> <td align="left" valign="top" style="background-color:#FDEDCE"><strong>In present matter, the High Court dismissed an application under Section 482 of the Code of Criminal Procedure, 1973 (CrPC). The Appellant sought the quashing of a First Information Report registered against him for offences punishable under Sections 376, 417, 504 and 506(2) of the Indian Penal Code, 1860 (IPC) and Sections 3(1)(u), (w) and 3(2)(vii) of The Scheduled Castes and Scheduled Tribes (Prevention of Atrocities Act, 1989 (as amended by the Amendment Act, 2015). The High Court rejected the application, noting that, though the relationship was with consent, it appears that there was a promise to marry and statement shows that later on, giving reason of caste of Complainant, promise was not kept. <br><br> The powers of the Court under Section 482 of CrPC are wide and the court is vested with a significant amount of discretion to decide whether or not to exercise them. The Court should be guarded in the use of its extraordinary jurisdiction to quash an FIR or criminal proceeding as it denies the prosecution the opportunity to establish its case through investigation and evidence. <br><br> This Court has repeatedly held that consent with respect to Section 375 of the IPC involves an active understanding of the circumstances, actions and consequences of the proposed act. An individual who makes a reasoned choice to act after evaluating various alternative actions (or inaction) as well as the various possible consequences flowing from such action or inaction, consents to such action. <br><br> In the present case, the "misconception of fact" alleged by the complainant is the Appellant's promise to marry her. Specifically in the context of a promise to marry, present Court has observed that there is a distinction between a false promise given on the understanding by the maker that it will be broken, and the breach of a promise which is made in good faith but subsequently not fulfilled. <br><br> Where the promise to marry is false and the intention of the maker at the time of making the promise itself was not to abide by it but to deceive the woman to convince her to engage in sexual relations, there is a "misconception of fact" that vitiates the woman's "consent". On the other hand, a breach of a promise cannot be said to be a false promise. To establish a false promise, the maker of the promise should have had no intention of upholding his word at the time of giving it. The "consent" of a woman under Section 375 is vitiated on the ground of a "misconception of fact" where such misconception was the basis for her choosing to engage in the said act. <br><br> The "consent" of a woman with respect to Section 375 of IPC must involve an active and reasoned deliberation towards the proposed act. To establish whether the "consent" was vitiated by a "misconception of fact" arising out of a promise to marry, two propositions must be established. The promise of marriage must have been a false promise, given in bad faith and with no intention of being adhered to at the time it was given. The false promise itself must be of immediate relevance, or bear a direct nexus to the woman's decision to engage in the sexual act. <br><br> The allegations in the FIR do not on their face indicate that the promise by the Appellant was false, or that the complainant engaged in sexual relations on the basis of this promise. There is no allegation in the FIR that when the Appellant promised to marry the complainant, it was done in bad faith or with the intention to deceive her. The Appellant's failure in 2016 to fulfil his promise made in 2008 cannot be construed to mean the promise itself was false. The allegations in the FIR indicate that the complainant was aware that there existed obstacles to marrying the Appellant since 2008, and that she and the Appellant continued to engage in sexual relations long after their getting married had become a disputed matter. Even thereafter, the complainant travelled to visit and reside with the Appellant at his postings and allowed him to spend his weekends at her residence. The allegations in the FIR belie the case that she was deceived by the Appellant's promise of marriage. Therefore, even if the facts set out in the complainant's statements are accepted in totality, no offence under Section 375 of the IPC has occurred. <br><br> With respect to the offences under the SC/ST Act, the WhatsApp messages were alleged to have been sent by the Appellant to the complainant, it is apparent that none of the offences set out are made out. The messages were not in public view, no assault occurred, nor was the Appellant in such a position so as to dominate the will of the complainant. Therefore, even if the allegations set out by the complainant with respect to the WhatsApp messages and words uttered are accepted on their face, no offence is made out under SC/ST Act (as it then stood). The allegations on the face of the FIR do not hence establish the commission of the offences alleged. The impugned judgment and order of the High Court is set aside. The FIR is quashed. Appeal is allowed.</strong></td> </tr> <tr> <td align="left" valign="top" ><strong></strong></td> </tr> <tr> <td align="left" valign="top" ><strong>Tags : FIR, Registration, Quashing of</strong></td> </tr> <tr> <td align="left" valign="top"> </td> </tr> <tr> <!--<td><strong>Source : <a target="_new" href="http://www.manupatrafast.com/">newsroom.manupatra.com</a></strong></td>--> <td align="left" valign="top"><strong>Source : newsroom.manupatra.com</strong></td> </tr> <tr> <td align="left" valign="top"> </td> </tr> <tr> <td align="left" valign="top">Regards</td> </tr> <tr> <td align="left" valign="top">Team Manupatra</td> </tr> <tr> <td align="left" valign="top"> </td> </tr> </table> </div> </body> </html>