WELL · 42-001-32779 · DISTRICT 6

Reed #1

Plugged

Anderson County · Slocum NW (Woodbine C) field  · Vertical

Reed #1 (API 42-001-32779) is a plugged well in Anderson County, plugged February 5, 2018, last operated by Petro-Chem Operating Company Inc.

The RRC has issued one drilling permit, issued January 2, 2018, permitted to 6,000 ft.

It was permitted by Petro-Chem Operating Company,Inc and has since transferred to Petro-Chem Operating Company Inc on the wellbore schedule.

Operator of record

Petro-Chem Operating Company Inc

Permitted by Petro-Chem Operating Company,inc; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitPetro-Chem Operating Company,incJan 2, 2018

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

6,000
total depth, ft
1
permits on file
Jan 2, 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 5, 2018

Surface location

31.612713, -95.496799

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Anderson 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
834366-99DrillPetro-Chem Operating Company,incDec 18, 2017Jan 2, 2018Jan 27, 20186,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 →

Luke42-001-32786

0.1 KM · Trueblood Resources, Inc. · Section with this well →

Queen City400
Newby550
Carrizo580
Carrizo630
Pecan Gap—
Woodbine—
Travis Peak—
Pettit—

10 TOPS · FIRST 8

Beeler42-001-32759

3.5 KM · Chestnut Explor. and Prod., Inc. · Section with this well →

James Lime—
Pecan Gap—
Pecan Gap—
Pettit—
Rodessa—
Sub-Clarksville—
Travis Peak—
Woodbine—

Fitzgerald42-001-32820

4.8 KM · Trueblood Resources, Inc. · Section with this well →

Carrizo554-175
James Lime—
Woodbine—
Travis Peak—
Sub-Clarksville—
Rodessa—
Pettit—
Pecan Gap—

Fitzgerald42-001-32837

4.8 KM · Trueblood Resources, Inc. · Section with this well →

Carrizo565-179
Woodbine—
James Lime—
Pecan Gap—
Pettit—
Rodessa—
Sub-Clarksville—
Travis Peak—

Fitzgerald42-001-32821

4.8 KM · Trueblood Resources, Inc. · Section with this well →

Carrizo536-151
Woodbine—
Travis Peak—
James Lime—
Rodessa—
Pettit—
Pecan Gap—
Sub-Clarksville—

Fitzgerald42-001-32819

4.8 KM · Trueblood Resources, Inc. · Section with this well →

Carrizo571-179
Woodbine—
Pecan Gap—
Pettit—
Rodessa—
Sub-Clarksville—
Travis Peak—
James Lime—

Fitzgerald42-001-32818

4.8 KM · Trueblood Resources, Inc. · Section with this well →

Carrizo579-179
Pecan Gap—
Pettit—
Rodessa—
Sub-Clarksville—
Travis Peak—
James Lime—
Woodbine—

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