WELL · 42-143-31220 · DISTRICT 9

Gaddy Unit #2H

Y

Erath County · Newark East (Barnett Shale) field · Temp Abandoned  · Horizontal

Gaddy Unit #2H (API 42-143-31220) is a horizontal well in Erath County operated by B.O.S.S. Petroleum L.L.C., completed February 18, 2008 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued May 29, 2007, permitted to 10,000 ft.

It was permitted by Xto Energy Inc. and has since transferred to B.O.S.S. Petroleum L.L.C. on the wellbore schedule.

Completion filings report 3 formation tops, including Smithwick, Bend, Barnett.

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

Operator of record

B.O.S.S. Petroleum L.L.C.

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

Bluff Dale, TX · P-5 Y, filed Oct 4, 2025 · (512) 913-1777

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleB.O.S.S. Petroleum L.L.C.
Production reportsXTO Energy Inc.through May 2010
Latest permitXTO Energy Inc.May 29, 2007

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

10,000
total depth, ft
2
permits on file
May 29, 2007
last permit issued
Feb 18, 2008
completed
0
cumulative oil, bbl
39.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 18, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Gaddy Unit G-13-235627Newark, East (Barnett Shale)B.O.S.S. Petroleum, L.L.C.1039.7KOct 2007 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1XTO Energy Inc.Feb 2008 → May 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
639513-98DrillXTO Energy Inc.Oct 15, 2007May 29, 2007Jun 19, 200710,000
639513-99DrillXTO Energy Inc.May 23, 2007May 29, 2007Jun 19, 200710,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-235627————

Formation tops

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

FormationMD ftSubsea
Smithwick4,237-3,235
Bend4,302-3,300
BarnettUPPER BARNETT4,648-3,646

Perforations

Perforated and open-hole intervals.

FromToType
5,2158,364Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62562212.25165 S
5.55,0838.75325 S
5.58,5328.75—

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
00Mar 26, 2009Feb 19, 2009—
00Jun 16, 2008Nov 5, 2007Yes
00Jun 3, 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/14331220, documented in the API reference.