WELL · 42-023-31713 · DISTRICT 9

Usg Martin #3121

Plugged

Baylor County · Baylor County Regular field  · Vertical

Usg Martin #3121 (API 42-023-31713) is a plugged well in Baylor County, plugged February 26, 2019, last operated by US Geophysical LLC.

The RRC has issued one drilling permit, issued November 7, 2018, permitted to 7,000 ft.

It was permitted by US Geophysical LLC and has since transferred to US Geophysical LLC on the wellbore schedule.

Operator of record

US Geophysical LLC

Permitted by US Geophysical LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitUS Geophysical LLCNov 7, 2018

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

7,000
total depth, ft
1
permits on file
Nov 7, 2018
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
Feb 26, 2019

Surface location

33.523570, -99.003453

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Baylor 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
846578-99DrillUS Geophysical LLCNov 7, 2018Nov 7, 2018Feb 18, 20197,000

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 →

Green SWD42-023-31726

3.7 KM · Allied Energy Operating, LLC · Section with this well →

Coleman Junction1,360-143
Thomas Sand1,540-323
Tannehill1,762-545
Palo Pinto—
Gunsight—
Home Creek—
Strawn—
Saddle Creek—

10 TOPS · FIRST 8

Reynolds42-023-31720

3.7 KM · Willowbend Investments, Inc. · Section with this well →

Coleman Junction400909
Gunsight1,040269
Tannehill1,340-31
Palo Pinto3,630-2,321
Caddo4,898-3,589
Conglomerate5,161-3,852
Mississippian5,348-4,039
Cisco—

10 TOPS · FIRST 8

Zinfandel42-023-31723

5.8 KM · Canan Operating, Inc. · Section with this well →

Palo Pinto3,034-1,860
Strawn4,749-3,575
Thomas Sand—
Canyon—
Cisco—
Coleman Junction—
Gunsight—
Home Creek—

10 TOPS · FIRST 8

Z42-023-31729

5.9 KM · Brower Oil & Gas Co., Inc. · Section with this well →

Palo Pinto3,025-1,844
Coleman Junction—
Tannehill—
Cisco—
Thomas Sand—
Canyon—
Strawn—
Gunsight—

10 TOPS · FIRST 8

Quisenberry A42-023-31711

6.3 KM · Dry Fork Production Co., LLC · Section with this well →

Coleman Junction1,20087
Saddle Creek1,485-198
Palo Pinto2,500-1,213
Home Creek2,675-1,388
Canyon3,076-1,789
Cisco—
Canyon—
Thomas Sand—

10 TOPS · FIRST 8

Covington42-023-31717

7.6 KM · Canan Operating, Inc. · Section with this well →

Coleman Junction1,850-651
Home Creek2,607-1,408
Palo Pinto3,135-1,936
Strawn3,994-2,795
Saddle Creek—
Cisco—
Gunsight—
Canyon—

10 TOPS · FIRST 8

W. T. Richardson42-009-43164

11.3 KM · Knobloch, Albert · Section with this well →

Thomas Sand540483
Gunsight1,250-227
Megargel—
Delmar—
Ward Sand—
Strawn—
Canyon—
Bryson—

10 TOPS · FIRST 8

Portwood -C-&-D-42-009-43170

11.6 KM · Myers, James B. · Section with this well →

Thomas Sand1,100
Gunsight1,400
Ward Sand—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—

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