WELL · 42-101-30775 · DISTRICT 11

Farm Land Reserve #1

Plugged

Cottle County · Wildcat field  · Vertical

Farm Land Reserve #1 (API 42-101-30775) is a plugged well in Cottle County, plugged March 4, 2024, last operated by Gunn Oil CO..

The RRC has issued one drilling permit, issued January 24, 2024, permitted to 9,000 ft.

It was permitted by Gunn Oil Company and has since transferred to Gunn Oil CO. on the wellbore schedule.

Operator of record

Gunn Oil Co.

Permitted by Gunn Oil Company; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitGunn Oil CompanyJan 24, 2024

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

9,000
total depth, ft
1
permits on file
Jan 24, 2024
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 4, 2024

Surface location

33.969057, -100.082052

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Cottle 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
896737-99DrillGunn Oil CompanyJan 22, 2024Jan 24, 2024Feb 24, 20249,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 4 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 →

L.K. Johnson42-101-30755

3.1 KM · NWG Operating LLC · Section with this well →

Gunsight3,300-1,636
Bend—
Cisco—
Coleman Junction—
Canyon—
Palo Pinto—
Rasperry—
Strawn—

10 TOPS · FIRST 8

L.K. Johnson42-155-30808

3.2 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,920-296
Tannehill2,440-816
Gunsite3,234-1,610
Cisco3,500-1,876
Canyon3,536-1,912
Caddo—
Bend—
Palo Pinto—

10 TOPS · FIRST 8

LK Johnson42-155-30810

3.3 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,924-315
Gunsite3,233-1,624
Canyon3,564-1,955
Bend—
Caddo—
Cisco—
Palo Pinto—
Raspberry—

10 TOPS · FIRST 8

Johnson, L. K.42-155-30815

4.6 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,967-347
Tannehill2,457-837
Gunsite3,325-1,705
Cisco3,629-2,009
Canyon3,730-2,110
Bend—
Palo Pinto—
Raspberry—

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