WELL · 42-413-33015 · DISTRICT 7

Treadwell #1

Plugged

Schleicher County · Wildcat field  · Vertical

Treadwell #1 (API 42-413-33015) is a plugged well in Schleicher County, plugged March 21, 2019, last operated by VX Operating LLC.

The RRC has issued one drilling permit, issued January 10, 2019, permitted to 2,500 ft.

It was permitted by VX Operating, LLC and has since transferred to VX Operating LLC on the wellbore schedule.

Operator of record

VX Operating LLC

Permitted by VX Operating, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitVX Operating, LLCJan 10, 2019

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

2,500
total depth, ft
1
permits on file
Jan 10, 2019
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Mar 21, 2019

Surface location

30.958265, -100.151279

OpenStreetMap → ·  Google Maps →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
848559-99DrillVX Operating, LLCJan 10, 2019Jan 10, 2019Feb 12, 20192,500

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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

McGregor Unit42-413-32747

3.7 KM · Telesis Operating Co., Inc. · Section with this well →

Gunsight2,651-361
Adams Branch3,792-1,502
Palo Pinto4,227-1,937

McGregor Unit42-413-32981

4.9 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,2001,114
Wolfcamp1,974340
Canyon3,750-1,436
Lime 41503,952-1,638
Strawn4,408-2,094
Ellenburger4,796-2,482
Cambrian5,540-3,226
San Angelo—

9 TOPS · FIRST 8

E.M. Clancy42-413-32934

5.0 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction—
Ellenburger—
San Angelo—
Strawn—
Wolfcamp—
Clear Fork—
Canyon—

E.M. Clancy42-413-32935

5.2 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,680
Wolfcamp2,650
Canyon3,950
Strawn4,490
San Angelo—
Ellenburger—
Coleman Junction—
Clear Fork—

9 TOPS · FIRST 8

Powell42-413-33007

6.2 KM · VX Operating, LLC · Section with this well →

Coleman Junction1,2001,118
Canyon3,881-1,563
Strawn4,002-1,684
San Angelo—
Ellenburger—
Clear Fork—
Wolfcamp—

Powell 'A'42-413-33001

6.5 KM · VX Operating, LLC · Section with this well →

Coleman Junction1,2501,063
Canyon3,931-1,618
Strawn4,256-1,943
Wolfcamp—
Clear Fork—
Ellenburger—
San Angelo—

Thornburg42-413-33000

7.2 KM · VX Operating, LLC · Section with this well →

Coleman Junction1,2001,106
Canyon3,881-1,575
Strawn4,437-2,131
Ellenburger—
Clear Fork—
San Angelo—
Wolfcamp—

Thornburg 2742-413-32999

7.6 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,422
Wolfcamp2,058
Canyon3,926
Strawn4,302
Ellenburger—
San Angelo—
Clear Fork—

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