WELL · 42-241-30897 · DISTRICT 3

Adams Ranch #1

N

Jasper County  · Vertical

Adams Ranch #1 (API 42-241-30897) is a permitted well in Jasper County filed by Texakota, Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 16, 2018, permitted to 13,000 ft.

Operator of record

Texakota, Inc.

Houston, TX · P-5 Y, filed Aug 6, 2021 · 214 permits on file · (310) 567-7469

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitTexakota, Inc.Jul 16, 2018
13,000
total depth, ft
1
permits on file
Jul 16, 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
—

Surface location

30.266730, -93.993854

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Jasper 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
842437-99DrillTexakota, Inc.Jul 16, 2018Jul 16, 2018—13,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 →

BP America A46942-241-30913

4.0 KM · BPX Operating Company · Section with this well →

Frio5,714-5,667
Jackson7,534-7,487
Yegua8,591-8,544
Wilcox—
Miocene (undifferentiated)—

Barracuda42-241-30924

4.5 KM · Atoka Operating, Inc. · Section with this well →

Wilcox—
Frio—
Jackson—
Miocene (undifferentiated)—
Yegua—

Ten Mile42-361-30993

5.3 KM · Atoka Operating, Inc. · Section with this well →

Hackberry - Disposal8,000
Opiela Sand - Disposal9,000
Yegua9,900
Frio—
Miocene (undifferentiated)—

H. J. Ballard42-241-30895

5.6 KM · Choice Exploration, Inc. · Section with this well →

Miocene (undifferentiated)2,950-2,916
Frio5,075-5,041
Jackson5,850-5,816
Nodosaria6,705-6,671
Yegua8,964-8,930
Upper DY Yegua9,240-9,206
Wilcox—

Oriskany A-15242-241-30920

5.9 KM · Ironroc Energy · Section with this well →

Catahoula3,977-3,946
Hackberry6,274-6,243
Yegua9,162-9,131
Yegua9,811-9,780
Yegua11,100-11,069
Wilcox—
Yegua—
Frio—

10 TOPS · FIRST 8

Yang42-241-30903

6.9 KM · Whitehead Resources, Ltd. · Section with this well →

Hackberry 6500 Sand6,368-6,341
Hackberry 16,608-6,581
Hackberry 36,935-6,908
Nodosaria 17,160-7,133
Wilcox—
Frio—
Jackson—
Miocene (undifferentiated)—

9 TOPS · FIRST 8

Yang42-241-30911

6.9 KM · Whitehead Resources, Ltd. · Section with this well →

Miocene (undifferentiated)2,740-2,710
Frio3,950-3,920
Wilcox—
Jackson—
Yegua—

Daffy42-241-30894

8.6 KM · Lep Development Company, LLC · Section with this well →

Miocene (undifferentiated)3,710-3,672
Frio4,750-4,712
Jackson7,568-7,530
Yegua8,360-8,322
Wilcox—

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