WELL · 42-335-35132 · DISTRICT 8

Coleman Estate #6802

Y

Mitchell County · Coleman Ranch N. (Clear Fork) field · Producing  · Vertical

Coleman Estate #6802 (API 42-335-35132) is a well in Mitchell County operated by Unitex Oil & Gas L.L.C., completed February 15, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 13, 2008, permitted to 3,400 ft.

Completion filings report one formation top, including Clear Fork.

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

Operator of record

Unitex Oil & Gas L.L.C.

Midland, TX · P-5 Y, filed Feb 4, 2026 · 96 permits on file · (432) 770-8831

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnitex Oil & Gas L.L.C.
Production reportsUnitex Oil & Gas, L.L.C.through Apr 2026
Latest permitUnitex Oil & Gas, L.L.C.Oct 13, 2008
3,400
total depth, ft
1
permits on file
Oct 13, 2008
last permit issued
Feb 15, 2009
completed
278K
cumulative oil, bbl
20
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 15, 2009
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; they carry 21 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Coleman Estate O-10-24237Coleman Ranch, N. (Clear Fork)Unitex Oil & Gas, L.L.C.21278K20Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 3,373 · prior 12 3,647(-8%)

0200400600202420252026

Chain of custody

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

  1. 1Kidd, Barron UlmerJan 1993 → Apr 1993
  2. 2Kidd Oil & Gas, LCMay 1993 → Jun 1994
  3. 3Allegro Operating, Inc.Jul 1994 → Jan 1999
  4. 4Brothers Production Company Inc.Mar 1999 → Mar 2000
  5. 5Cowboys Resources Corp.Apr 2000 → Jan 2008
  6. 6Unitex Oil & Gas, L.L.C.Feb 2008 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
672635-99DrillUnitex Oil & Gas, L.L.C.Oct 7, 2008Oct 13, 2008Nov 12, 20083,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-24237————

Formation tops

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

FormationMD ftSubsea
Clear ForkUPPER CLEARFORK2,760-567
Clear ForkMIDDLE CLEARFORK3,000-807
Clear ForkLOWER CLEARFORK3,250-1,057

Perforations

Perforated and open-hole intervals.

FromToType
3,1073,173Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62539012.25250 S
5.53,4007.875800 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
00Feb 9, 2010Aug 5, 2009Yes
00Dec 7, 2009——

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