WELL · 42-287-31618 · DISTRICT 3

Daniels #1

Plugged

Lee County · Giddings (Austin Chalk Gas) field  · Vertical

Daniels #1 (API 42-287-31618) is a plugged well in Lee County, plugged June 21, 2002, last operated by Emerald Operating Company Inc..

The RRC has issued one drilling permit, issued May 23, 1984, permitted to 9,500 ft.

It was permitted by U. S. Operating, Inc. and has since transferred to Emerald Operating Company Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Pecan Gap, Austin Chalk, Eagle Ford.

Operator of record

Emerald Operating Company Inc.

Permitted by U. S. Operating, Inc.; the EWA schedule now lists a different operator.

Based in
Plano, TX
P-5 status
Inactive (I)
P-5 last filed
Aug 5, 2008
Permits on file
22
Phone
(972) 578-7722

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEmerald Operating Company Inc.
Production reportsArrow Exploration Companythrough Dec 2000
Latest permitU. S. Operating, Inc.May 23, 1984

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

9,500
total depth, ft
1
permits on file
May 23, 1984
last permit issued
Jul 19, 1984
completed
0
cumulative oil, bbl
32.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 19, 1984
Shut in
—
Plugged
Jun 21, 2002

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Daniels G-3-141906Giddings (Austin Chalk, Gas)Emerald Operating Company, Inc.1032.4KJan 1993 – Jun 2002
— O-3-17831——000—

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Tex-Lee Operating CompanyJul 1993 → Aug 1994
  2. 2Arrow Exploration CompanyOct 1994 → Dec 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
239866-99DrillU. S. Operating, Inc.May 9, 1984May 23, 1984—9,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-141906————
—— O-3-17831————

Formation tops

As filed on W-2/G-1. Subsea from 311 ft elevation.Download CSV →

FormationMD ftSubsea
Pecan Gap7,488-7,177
Austin Chalk8,290-7,979
Eagle FordEAGLEFORD8,990-8,679

Perforations

Perforated and open-hole intervals.

FromToType
8,3548,537Perforated
8,7278,977Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,95012.251,150 S
5.59,1008.5500 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Aug 20, 1992Aug 3, 1992—
00Aug 11, 1992——
00May 22, 1985Apr 15, 1985—
00Aug 24, 1984Aug 8, 1984—
00Aug 18, 1984Aug 8, 1984—

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.

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