Rodriguez v. Shartle

Decision Date04 November 2012
Docket NumberCivil Action No. 12-1656 (RBK)
PartiesRAY RODRIGUEZ, Petitioner, v. J.T. SHARTLE, Respondent.
CourtU.S. District Court — District of New Jersey

NOT FOR PUBLICATION

MEMORANDUM OPINION

This matter comes before this Court upon: (a) receipt of a clarification graciously provided by Petitioner's sentencing court,1 see Docket Entry No. 6; and (b) Respondent's prompt filing of an expedited answer.2

For the reasons detailed below, the Court will construe the Petition within as asserting challenges based on the holding of Ruggiano v. Reish, 307 F.3d 121 (3d Cir. 2002), and will dismiss these challenges with prejudice.3

Petitioner's challenges based on the holding of Barden v. Keohane, 921 F.2d 476 (3d Cir. 1991), and/or Willis v. United States, 438 F.2d 923 (5th Cir. 1971), and/or Kayfez v. Gasele, 993 F. 2d 1288 (7th Cir. 1993), that is, provided such challenges were intended, will be dismissed as improperly raised in thismatter, pursuant to Habeas Rule 2.4 Out of abundance of caution, the Court will direct the Clerk to open a new and separate habeas matter for Petitioner with a presumption that Petitioner might have wished to raise such challenges. On the basis of such presumption, and in light of the information provided in the attachment to the Petition, these challenges will be dismissed without prejudice, as unexhausted. Petitioner, however, will be granted leave to file an amended pleading, provided that such amended pleading shows due administrative exhaustion of his Barden and/or Willis and/or Kayfez challenges and states facts supporting these claims.5

I. BACKGROUND

Petitioner commenced this matter without submitting his in forma pauperis application and without paying his filing fee. See Docket Entry No. 1. The Court, therefore, directed administrative termination of this matter, and allowed Petitioner an opportunity to cure the deficiency of his submission. See Docket Entry No. 2. Petitioner, thereafter, cured said deficiency by prepaying his filing fee. Correspondingly, the Court screened the Petition pursuant to Habeas Rule 4.6

The Petition proved to be of less than exemplar clarity, since it: (a) asserted that Petitioner was seeking a § 2241 writpursuant to the holding of Ruggiano v. Reish on the grounds that Judge Davis directed retroactive adjustment of Petitioner's federal sentence by uttering certain, not elaborated in the Petition, oral statements during Petitioner's federal sentencing proceedings, see Docket Entry No. 1, at 6-7 (citing, exclusively, the United States Sentencing Guidelines § 5G1.3, Ruggiano and its progeny as legal bases for Petitioner's claim); and yet, simultaneously, (b) used the term "credit" commonly employed by the litigants seeking recalculation of their prison terms pursuant to the holdings of Barden, 921 F.2d 476, or Willis, 438 F.2d 923, or Kayfez, 993 F. 2d 1288. See Docket Entry No. 1, at 7 and 11-12. Petitioner's attachment to his Petition suggested that, administratively, he raised his claims only to his warden. See id.

Although Petitioner's § 2241 challenges appeared subject to dismissal without prejudice (as administratively unexhausted), the Court - prior to entering such dismissal - examined Petitioner's information available at the BOP website in order to determine whether circumstances warranting excuse of exhaustion were present.7 The Court's review of Petitioner's BOPinformation revealed that his projected release date was August 7, 2013. See . Since Petitioner's pleading maintained that, pursuant to Judge Davis' downward adjustment directive, Petitioner's release from federal confinement had to take place ten months sooner, that is, on November 7, 2012, this Court found it warranted to excuse Petitioner's failure to exhaust his Ruggiano challenges. See Docket Entry No. 3, at 5 and n. 3 (noting, with disapproval, Petitioner's election to omit stating his projected release date in his Petition and pointing out that, "had this Court not checked Petitioner's BOP information . . . , Petitioner could, hypothetically, overserve his imposed term of imprisonment").

Correspondingly, the Court directed: (a) Respondent to file an expedited answer addressing Petitioner's Ruggiano claims, see id. at 7; and (b) the Clerk to serve a complimentary copy of the Court's order on Judge Davis so to inform Judge Davis ofPetitioner's Ruggiano-based position and, if possible, obtain Judge Davis' clarification as to the federal sentence imposed upon Petitioner. See id. 6 and 8-9.

As noted supra, Judge Davis swiftly and graciously provided said clarification, stating, in pertinent part, as follows:

Contrary to the assertions in Mr. Rodriguez's Petition [filed] under 28 U.S.C. § 2241, I did not grant a ten-month adjustment to Mr. Rodriguez's sentence. At all times, I intended that Mr. Rodriguez's July 12, 2010 sentence would run consecutively to any other sentence that Mr. Rodriguez must serve. My June 16, 2011 Order merely [recommended the BOP to] grant[] Mr. Rodriguez a sentencing credit, which I referred to the Federal Bureau of Prisons for calculation — a policy which I have maintained for more than two decades. To the extent that the Bureau of Prisons has calculated that Mr. Rodriguez is entitled to a sentencing credit of zero-days, such a finding does not conflict with my Order.

Docket Entry No. 6.

Meanwhile, Respondent obtained Petitioner's sentencing transcript and, in reliance on the same and in full accord with the above-quoted Judge Davis' clarification, asserted that Petitioner was never granted any downward adjustment. See Docket Entry No. 7, at 1-2 (quoting Petitioner's sentencing transcript and correctly distilling Judge Davis': (a) keen awareness of Petitioner's recidivist record; and (b) lack of any intent to resort to his power to grant downward adjustment).

II. DISCUSSION
A. Difference Between an "Adjustment" and "Credits"

Any computation of a federal sentence starts with a determination when that sentence commences and to what extent the sentenced inmate can receive credit for time spent in custody prior to the commencement of sentence. See Chambers v. Holland, 920 F. Supp. 618, 621 (M.D. Pa.), aff'd, 100 F.3d 946 (3d Cir. 1996).

For offenses committed on or after November 1, 1987, determinations regarding the commencement of federal sentence are governed by 18 U.S.C. § 3585(a), and the issue of prior custody credit is governed by 18 U.S.C. § 3585(b).8 The authority of the Attorney General to compute sentences has been further delegated to the BOP by operation of 28 C.F.R. § 0.96 (1996). See United States v. Brann, 990 F.2d 98, 103—04 (3d Cir. 1993).

"A sentence to a term of imprisonment commences on the date the defendant is received in custody awaiting transportation to, or arrives voluntarily to commence service of sentence at, the official detention facility at which the sentence is to beserved."9 18 U.S.C. § 3585(a). A related provision, Section 3584 clarifies:

Imposition of concurrent or consecutive term. - If multiple terms of imprisonment are imposed on a defendant at the same time, or if a term of imprisonment is imposed on a defendant who is already subject to an undischarged term of imprisonment, the terms may run concurrently or consecutively, except that the terms may not run consecutively for an attempt and for another offense that was the sole objective of the attempt. Multiple terms of imprisonment imposed at the same time run concurrently unless the court orders or the statute mandates that the terms are to run consecutively. Multiple terms of imprisonment imposed at different times run consecutively unless the court orders that the terms are to run concurrently.

18 U.S.C. § 3584(s).

Thus, an inmate's federal sentence begins to run upon his/her receipt in federal custody - unless the district court imposing the inmate's federal sentence expressly directs either full or partial retroactive concurrence with another, already existing and still running sentence served by the inmate. See Ruggiano, 307 F.3d at 132 (sentencing court has authority under 18 U.S.C. § 3584 and United States Sentencing Guidelines § 5G1.3(c) to order a federal sentence to be fully and retroactively concurrent to a state sentence the defendant was already serving); see also Oregon v. Ice, 555 U.S. 160, 168-69(2010) (judges have traditionally had broad discretion in selecting whether the sentence they impose will run consecutively or concurrently with respect to other sentences that they impose, or that have been imposed in other proceedings, even state proceedings); accord Setser v. U.S., 132 S. Ct. 1463.10

Due to the unique power of federal judiciary to direct such retroactive concurrence, it has been numerously observed that a district court's order directing said concurrence cannot be qualified as a "credit" against an inmate's sentence.

The Guidelines cautions sentencing courts that, "[t]o avoid confusion with the Bureau of Prisons' . . . authority provided under 18 U.S.C. § 3585(b) to grant credit . . . the [Sentencing] Commission recommends that any downward departure under . . . application note [3(E) in § 5G1.3] be clearly stated . . . as a downward departure pursuant to § 5G1.3(c), rather than as a credit for time served." U.S.S.G. § 5G1.3 cmt. n.3(E); seealsoRuggiano, 307 F.3d at 133 ("[W]e encourage sentencing courts in the future to avoid using the term 'credit' to refer to § 5G1.3 adjustments so as not to engender any unnecessary confusion"). In Ruggiano, we [expressly guided] that sentencing courts should use the term "adjustment," rather than "credit" or "downward departure," in order to avoid confusionwhen applying Guidelines § 5G1.3. [SeeRuggiano,] 307 F.3d at 133. However, Application Note 3(E) to Guidelines § 5G1.3, which came into effect after Ruggiano, indicates that the appropriate terminology is "downward departure."

United States v. Gaskins, 393 F. App'x 910, 914 and n. 2 (3d Cir. 2010).

In contrast, § 3585(b) governs the...

To continue reading

Request your trial

VLEX uses login cookies to provide you with a better browsing experience. If you click on 'Accept' or continue browsing this site we consider that you accept our cookie policy. ACCEPT