WELL · 42-103-03196 · DISTRICT 8

Tubb -A- #6

Y

Crane County · Sand Hills (Judkins) field · Producing  · Vertical

Tubb -A- #6 (API 42-103-03196) is a permitted well in Crane County filed by Millwee Oil, Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued December 14, 2006, permitted to 4,400 ft.

Completion filings report 3 formation tops, including Judkins, McKnight, Tubb.

Its 2 leases have reported 204K barrels of oil and 4.3M mcf of gas since January 1993, last reporting in July 2026. The leases carry 23 wells, so these are lease totals, not this well alone.

Operator of record

Millwee Oil Inc.

Midland, TX · P-5 Y, filed May 4, 2026 · 19 permits on file · (432) 770-3222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMillwee Oil Inc.
Production reportsMillwee Oil, Inc.through Apr 2026
Latest permitMillwee Oil, Inc.Dec 14, 2006
4,400
total depth, ft
1
permits on file
Dec 14, 2006
last permit issued
—
completed
204K
cumulative oil, bbl
4.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
—
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 2 leases this well is completed on; they carry 23 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Tubb -a- /Tubb Zone/ O-10-5284Sand Hills (Tubb)Millwee Oil, Inc.931.2K452KJan 1993 – Jul 2026
Tubb -A- O-10-21848Sand Hills (Judkins)Millwee Oil, Inc.14173K3.85MJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 20,115 · prior 12 36,087(-44%)

05K10K202420252026

Oil, barrels lease total

Last 12 months 3,440 · prior 12 2,945(+17%)

0200400600202420252026

Chain of custody

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

  1. 1Fina Oil & Chemical CompanyJan 1993 → Sep 1994
  2. 2Millwee Oil, Inc.Oct 1994 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
629714-99RecompletionMillwee Oil, Inc.Nov 29, 2006Dec 14, 2006Oct 11, 20074,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-5284————
—— O-10-21848————

Formation tops

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

FormationMD ftSubsea
Judkins2,650-107
McKnight3,200-657
Tubb4,220-1,677

Perforations

Perforated and open-hole intervals.

FromToType
2,8002,969Perforated
3,3013,325Perforated
4,2294,400Open hole
—2,969Perforated
—4,500Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1051413.75160 S
74,2298.75225 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
00Jan 11, 2008Oct 22, 2007—
00Jan 4, 2008——
00Jan 12, 1984Aug 20, 1971—
00Jan 12, 1984——

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.

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