WELL · 42-371-39976 · DISTRICT 8

William Bonney SWD #1

WaterY

Pecos County · Wolfbone (Trend Area) field · Injection  · Vertical

William Bonney Swd #1 (API 42-371-39976) is a well in Pecos County operated by Gordy Oil Company, completed May 13, 2019 and listed as injection on the RRC schedule.

The RRC has issued one drilling permit, issued February 6, 2019, permitted to 6,600 ft.

Completion filings report 10 formation tops, including Rustler, Yates, Seven Rivers, Queen.

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

It holds an active disposal or injection permit, with 2.5M barrels injected in the 12 months reported through April 2026; TexNet located 0 M2+ earthquakes within 10 km over the last two years.

Operator of record

Gordy Oil Company

Houston, TX · P-5 Y, filed Feb 4, 2026 · 151 permits on file · (877) 231-2351

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGordy Oil Company
Production reportsnone
Latest permitGordy Oil CompanyFeb 6, 2019
6,600
total depth, ft
1
permits on file
Feb 6, 2019
last permit issued
May 13, 2019
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 13, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

30.916149, -102.787648

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Pecos County.

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
William Bonney SWD O-10-53465Wolfbone (Trend Area)Gordy Oil Company100May 2019 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
849115-99DrillGordy Oil CompanyJan 23, 2019Feb 6, 2019Apr 2, 20196,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-53465————

Formation tops

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

FormationMD ftSubsea
Rustler1,1751,746
Yates2,675246
Seven Rivers2,787134
Queen3,020-99
Grayburg3,807-886
Glorieta——
O'Brien——
Soma——
Toborg——
Tubb——

Perforations

Perforated and open-hole intervals.

FromToType
4,6656,209Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,58512.25395 S
74,6658.75590 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
00May 8, 2020Nov 8, 2019Yes

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

BSC-SWD42-371-39710

0.9 KM · Gordy Oil Company · Section with this well →

Rustler1,1231,772
Yates2,575320
Seven Rivers2,696199
Queen2,929-34
Grayburg3,695-800
O'Brien—
Soma—
Toborg—

10 TOPS · FIRST 8

Fat Boy42-371-39645

1.1 KM · Gordy Oil Company · Section with this well →

Rustler1,2201,748
Yates2,646322
Seven Rivers2,820148
Queen3,044-76
Grayburg3,850-882
O'Brien—
Glorieta—
Tubb—

10 TOPS · FIRST 8

Don Julio42-371-39551

1.1 KM · Gordy Oil Company · Section with this well →

Rustler1,2201,749
Yates2,646323
Seven Rivers2,820149
Queen3,044-75
Grayburg3,850-881
Toborg—
Glorieta—
O'Brien—

13 TOPS · FIRST 8

Doc Holliday SWD42-371-39977

1.2 KM · Gordy Oil Company · Section with this well →

Rustler1,1701,708
Yates2,647231
Seven Rivers2,778100
Queen3,035-157
Grayburg3,817-939
Glorieta—
O'Brien—
Capitan—

12 TOPS · FIRST 8

Rocker42-371-39850

1.5 KM · Gordy Oil Company · Section with this well →

Rustler1,2101,684
Yates2,704190
Seven Rivers2,83757
Queen3,109-215
Grayburg3,924-1,030
Soma—
Glorieta—
O'Brien—

10 TOPS · FIRST 8

Casa Nobles42-371-40093

1.6 KM · Gordy Oil Company · Section with this well →

Rustler1,2951,577
Yates2,703169
Seven Rivers2,83636
Queen3,111-239
Grayburg3,916-1,044
Glorieta—
O'Brien—
Soma—

10 TOPS · FIRST 8

Low Rider42-371-39852

1.6 KM · Gordy Oil Company · Section with this well →

Rustler1,2201,674
Yates2,701193
Seven Rivers2,83361
Queen3,107-213
Grayburg3,905-1,011
Soma—
Glorieta—
O'Brien—

10 TOPS · FIRST 8

Riazul42-371-40094

1.6 KM · Gordy Oil Company · Section with this well →

Rustler1,2951,577
Yates2,700172
Seven Rivers2,83240
Queen3,101-229
Grayburg3,877-1,005
Tubb—
O'Brien—
Glorieta—

10 TOPS · FIRST 8

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

2.5M
bbl, last 12 reported months
13.1M
bbl, all reported
Apr 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000117802W-14 DisposalActive15,0002,3224,645–6,600

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 2,502,795 · prior 12 2,130,976(+17%)

0200K400K20252026

TexNet catalog via USGS

Seismicity near this well

0
M2+ events within 10 km, last 2 years
—
largest

A proximity count, not an attribution. How to read it →

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/37139976, documented in the API reference.