WELL · 42-503-42449 · DISTRICT 13

Logan #3

N

Young County  · Vertical

Logan #3 (API 42-503-42449) is a permitted well in Young County filed by Texas Shallow Oil & Gas, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued February 12, 2020, permitted to 700 ft.

Operator of record

Texas Shallow Oil & Gas, LLC

Graham, TX · P-5 Y, filed May 29, 2025 · 20 permits on file · (940) 456-0520

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitTexas Shallow Oil & Gas, LLCFeb 12, 2020
700
total depth, ft
1
permits on file
Feb 12, 2020
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
—

Surface location

33.372457, -98.454839

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Young 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
861814-99DrillTexas Shallow Oil & Gas, LLCFeb 11, 2020Feb 12, 2020—700

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.

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 →

Williams, Mrs., A42-503-42537

0.6 KM · Alcorn, Jerry D. · Section with this well →

Breckenridge Lime175933
Breackenridge Lime175933
Trinity400708
Gunsight605503
Gunsight—
Herron City—
Cisco—
Canyon—

12 TOPS · FIRST 8

Prideaux, Inez42-009-43233

4.0 KM · White Knight Production LLC · Section with this well →

Gunsight500555
Cisco—
Bryson—
Canyon—
Davidson—
Delmar—
Megargel—
Strawn—

10 TOPS · FIRST 8

Stewart Deep42-503-42512

4.2 KM · B.O.L.D. Oil and Gas, LLC · Section with this well →

Gunsight450630
Caddo4,000-2,920
Palo Pinto—
Atoka—
Bryson—
Buttram—
Canyon—
Cisco—

10 TOPS · FIRST 8

Stewart -A-42-503-42496

4.2 KM · W T X Capital Investments, LLC · Section with this well →

Gunsight550550
Buttram—
Caddo—
Canyon—
Cisco—
Herron City—
Palo Pinto—
Strawn—

10 TOPS · FIRST 8

Prideaux42-237-40595

4.4 KM · Best Petroleum Explorations,inc. · Section with this well →

Strawn3,591-2,504
Caddo4,550-3,463
Atoka—
Gunsight—
Palo Pinto—
Village Bend—
Weir—
Canyon—

10 TOPS · FIRST 8

P-Mac42-503-82538

4.4 KM · Rogers Drilling Co., Inc. · Section with this well →

Gunsight698431
Gunsight714415
Cisco1,390-261
Cisco1,390-261
Palo Pinto2,466-1,337
Strawn2,798-1,669
Strawn2,798-1,669
Buttram—

13 TOPS · FIRST 8

R. O. Prideaux, Unit42-503-42428

4.8 KM · Stewart Construction · Section with this well →

Gunsight690442

Matlock42-009-43107

5.1 KM · Paladin Operating · Section with this well →

Megargel—
Strawn—
Gunsight—
Delmar—
Davidson—
Cisco—
Thomas Sand—
Canyon—

10 TOPS · FIRST 8

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