WELL · 42-159-30542 · DISTRICT 6

New Hope Deep Unit #76D

Y

Franklin County · New Hope (Smackover) field · Producing  · Vertical

New Hope Deep Unit #76D (API 42-159-30542) is a well in Franklin County operated by J.P. Oil Company Inc., completed April 29, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 28, 2007, permitted to 12,800 ft.

It was permitted by Xto Energy Inc. and has since transferred to J.P. Oil Company Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including BMA, Pittsburg, Elledge, Travis Peak.

No lease production has been reported under this well’s leases.

Operator of record

J.P. Oil Company Inc.

Permitted by XTO Energy Inc.; the EWA schedule now lists a different operator.

Based in
Lafayette, LA
P-5 status
Active (A)
P-5 last filed
May 5, 2026
Phone
(337) 234-1170

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJ.P. Oil Company Inc.
Production reportsJ.P. Oil Company, Inc.through Mar 2026
Latest permitXTO Energy Inc.Aug 28, 2007

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

12,800
total depth, ft
1
permits on file
Aug 28, 2007
last permit issued
Apr 29, 2008
completed
0
cumulative oil, bbl
1.47M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 29, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
New Hope Deep Unit G-6-238119New Hope (Smackover)J.P. Oil Company, Inc.101.47MApr 2008 – Jul 2026

Gas, mcf lease total

Last 12 months 41,833 · prior 12 49,201(-15%)

05K10K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1XTO Energy Inc.Apr 2008 → Oct 2023
  2. 2J.P. Oil Company, Inc.Nov 2023 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
643330-99DrillXTO Energy Inc.Jul 27, 2007Aug 28, 2007Feb 29, 200812,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-238119————

Formation tops

As filed on W-2/G-1. Subsea from 451 ft elevation.Download CSV →

FormationMD ftSubsea
BMA7,354-6,903
Pittsburg7,905-7,454
Elledge8,180-7,729
Travis Peak9,197-8,746
Cotton Valley9,652-9,201

Perforations

Perforated and open-hole intervals.

FromToType
11,89612,347Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62575812.25290 S
5.512,4858.751,940 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Aug 7, 2009Jun 23, 2008Yes
00Aug 23, 2008——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/15930542, documented in the API reference.