WELL · 42-429-37060 · DISTRICT 7

Stevenson-Jones Unit #40

Y

Stephens County · Stephens County Regular field · Producing  · Vertical

Stevenson-Jones Unit #40 (API 42-429-37060) is a well in Stephens County operated by Petex, completed July 25, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 6, 2023, permitted to 3,350 ft.

Completion filings report 10 formation tops, including Home Creek - Disposal, Winchell, Palo Pinto, Strawn.

Its lease has reported 2.16M barrels of oil and 249K mcf of gas since January 1993, last reporting in July 2026. The lease carries 37 wells, so these are lease totals, not this well alone.

Operator of record

Petex

Breckenridge, TX · P-5 Y, filed May 4, 2026 · 124 permits on file · (254) 559-5453

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetex
Production reportsPetexthrough Apr 2026
Latest permitPetexJun 6, 2023
3,350
total depth, ft
1
permits on file
Jun 6, 2023
last permit issued
Jul 25, 2023
completed
2.16M
cumulative oil, bbl
249K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 25, 2023
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

32.732165, -98.923288

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Stephens 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; they carry 37 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Stevenson-Jones Unit O-8-10661Stephens County RegularPetex372.16M249KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 32,293 · prior 12 32,354(0%)

02K4K202420252026

Gas, mcf lease total

Last 12 months 799 · prior 12 239(+234%)

05001K202420252026

Chain of custody

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

  1. 1Parker & Parsley Development Co.Jan 1993 → Dec 1994
  2. 2Merit Energy CompanyJan 1995 → Mar 2002
  3. 3Breck Operating Corp.Apr 2002 → Jul 2019
  4. 4PetexAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
890101-99DrillPetexApr 26, 2023Jun 6, 2023Jun 28, 20233,350

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-10661————

Formation tops

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

FormationMD ftSubsea
Home Creek - Disposal667575
Winchell786456
Palo Pinto1,318-76
StrawnSTRAWN - DISPOSAL2,106-864
Smithwick3,122-1,880
Breckenridge Sand - Disposal——
CiscoCISCO SAND - DISPOSAL——
Swastika - Disposal——
Unidentified-County Regular - DI——
Unidentified-County Regular (Gas——

Perforations

Perforated and open-hole intervals.

FromToType
3,1363,146Open hole
3,1803,190Open hole
3,2003,210Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62523012.25145 S
5.53,3507.875235 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
00Nov 14, 2023Oct 10, 2023Yes

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.

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 →

Southeast Breckenridge Unit42-429-34562

2.2 KM · Mobil Producing TX. & N.M. Inc. · Section with this well →

Home Creek568642
Winchell700510
Ranger Winchell700510
Palo Pinto1,228-18
Capps1,639-429
Strawn2,010-800
Caddo3,137-1,927

Akin-Wright42-429-33123

4.7 KM · S.B. Street Operating, Inc. · Section with this well →

Strawn2,411-1,107
Caddo3,005-1,701
Congl3,820-2,516

R. Stoker 'B'42-429-36414

5.0 KM · Basa Resources, Inc. · Section with this well →

Caddo3,200-1,927
Big Saline3,842-2,569
Marble Falls4,058-2,785

Curry Unit42-429-37038

5.4 KM · Basa Resources, Inc. · Section with this well →

Strawn2,244-953
Caddo3,214-1,923
Jennings - Disposal—
Home Creek - Disposal—
Cisco—
Breckenridge Sand - Disposal—
Bend—
Unidentified-County Regular - DI—

10 TOPS · FIRST 8

R. Stoker42-429-36415

5.8 KM · Basa Resources, Inc. · Section with this well →

Wichell Limestone1,036244
Palo Pintto Limestone1,508-228
Capps Limestone2,254-974
Caddo3,212-1,932

Curry Unit42-429-37040

6.2 KM · Basa Resources, Inc. · Section with this well →

Strawn2,245-975
Caddo3,209-1,939
Unidentified-County Regular - DI—
Breckenridge Sand - Disposal—
Bend—
Unidentified-County Regular (Gas—
Swastika - Disposal—
Jennings - Disposal—

10 TOPS · FIRST 8

Caldwell, C.M.42-429-36220

6.4 KM · McNallen Oil Co., Inc. · Section with this well →

Strawn2,766-1,527
Caddo3,222-1,983
Caddo3,222-1,983
Duffer3,632-2,393
Home Creek - Disposal—
Unidentified-County Regular (Gas—
Unidentified-County Regular - DI—
Swastika - Disposal—

12 TOPS · FIRST 8

Ranger42-429-37019

7.9 KM · Petex · Section with this well →

Caddo3,196-1,971
Swastika - Disposal—
Strawn—
Jennings - Disposal—
Home Creek - Disposal—
Breckenridge Sand - Disposal—
Cisco—
Bend—

10 TOPS · FIRST 8

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