WELL · 42-413-33031 · DISTRICT 7

Wallace 68 #2

Plugged

Schleicher County · Wildcat field  · Vertical

Wallace 68 #2 (API 42-413-33031) is a plugged well in Schleicher County, plugged November 7, 2023, last operated by Fossil Petroleum LLC.

The RRC has issued one drilling permit, issued October 6, 2023, permitted to 6,600 ft.

It was permitted by Fossil Petroleum LLC and has since transferred to Fossil Petroleum LLC on the wellbore schedule.

Operator of record

Fossil Petroleum LLC

Permitted by Fossil Petroleum LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitFossil Petroleum LLCOct 6, 2023

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

6,600
total depth, ft
1
permits on file
Oct 6, 2023
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
Nov 7, 2023

Surface location

30.981799, -100.569084

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
894296-99DrillFossil Petroleum LLCOct 3, 2023Oct 6, 2023Oct 25, 20236,600

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 →

Wallace 6842-413-33024

0.4 KM · Fossil Petroleum LLC · Section with this well →

San Angelo1,0301,219
Clear Fork2,590-341
Coleman Junction3,210-961
Wolfcamp3,890-1,641
Canyon6,348-4,099
Ellenburger—
Strawn—

Lloyd '18'42-413-31660

4.6 KM · Toc Energy Resources, LLC · Section with this well →

Clear Fork1,808544
Spraberry3,265-913
Wolfcamp4,098-1,746
Canyon5,058-2,706

Gardenia42-413-33030

7.0 KM · McCammon Oil & Gas, Inc. · Section with this well →

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

Barrow42-413-31742

7.9 KM · TXP, Incorporated · Section with this well →

Leonard3,192-749
Wolfcamp4,152-1,709
Canyon6,046-3,603
Canyon6,552-4,109

Whitten, L.I.42-413-10333

8.4 KM · TXP, Incorporated · Section with this well →

Pozo Rico (Wolfcamp)5,058-2,590
Canyon6,199-3,731
Strawn6,965-4,497
Wolfcamp—
Clear Fork—
Coleman Junction—
Ellenburger—
San Angelo—

C.G.M.42-413-32064

9.3 KM · Discovery Operating, Inc. · Section with this well →

Wolfcamp4,724-2,233
Canyon6,346-3,855

Jackson42-413-32238

11.5 KM · Pogo Producing Co. · Section with this well →

Wichita-Albany3,272-864
Dean3,606-1,198
Wolfcamp3,757-1,349

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