TEXAS · WELLS · KENT COUNTY · STEWART LEASE · API 42-263-31548 · DISTRICT 7B

Stewart #1

Plugged

Kent County · S-M-S (Canyon Sand) field  · Vertical

Stewart #1 (API 42-263-31548) is a plugged well in Kent County, plugged July 11, 2001, last operated by Petex.

The RRC has issued one drilling permit, issued March 6, 1995, permitted to 7,000 ft.

It was permitted by Dynamic Production, Inc. and has since transferred to Petex on the wellbore schedule.

Completion filings report one formation top, including Canyon.

Its lease has reported 238K barrels of oil since May 1995, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Petex

Permitted by Dynamic Production, Inc.; the EWA schedule now lists a different operator.

Based in
Breckenridge, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 24, 2026
Permits on file
124
Phone
(254) 559-5453

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetex
Production reportsPetexthrough Apr 2026
Latest permitDynamic Production, Inc.Mar 6, 1995

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

7,000
total depth, ft
1
permits on file
Mar 6, 1995
last permit issued
May 13, 1995
completed
238K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 13, 1995
Shut in
—
Plugged
Jul 11, 2001

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; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Stewart O-11-67399S-M-S (Canyon Sand)Petex4238K0May 1995 – Jul 2026

Oil, barrels lease total

Last 12 months 1,033 · prior 12 1,380(-25%)

0100200300202420252026

Chain of custody

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

  1. 1Dynamic Production, Inc.May 1995 → Mar 2017
  2. 2PetexApr 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
433562-99DrillDynamic Production, Inc.Mar 6, 1995Mar 6, 1995Mar 17, 19957,000

Completions

CompletedLeaseFieldOperatorStatusDepth
May 13, 1995Stewart O-11-67399S-M-S (Canyon Sand)PetexPlugged—

Formation tops

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

FormationMD ftSubsea
CanyonCANYON SAND6,030-3,913
CanyonCANYON REEF6,632-4,515

Perforations

Perforated and open-hole intervals.

FromToType
6,0416,064Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37522217.5210 S
8.6251,61211235 S
4.56,7257.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
00Jun 23, 1995Jun 8, 1995Yes
00Jun 19, 1995——

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