WELL · 42-077-34825 · DISTRICT 9

Edwards C #3

Plugged

Clay County · Dillard W. (Caddo) field  · Vertical

Edwards C #3 (API 42-077-34825) is a plugged well in Clay County, plugged January 24, 2003, last operated by Lane Operating Company.

The RRC has issued 2 drilling permits (amended once) between 2001 and 2002, permitted to 6,700 ft.

Completion filings report 3 formation tops, including Bryson, Caddo, Ellenburger.

Its 2 leases have reported 7.97K barrels of oil and 31.5K mcf of gas since October 2001, last reporting in March 2003. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Lane Operating Company

Wichita Falls, TX · P-5 Inactive, filed Jan 31, 2020 · 134 permits on file · (940) 322-0744

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLane Operating Company
Production reportsLane Operating Companythrough Jan 2003
Latest permitLane Operating CompanyMar 5, 2002
6,700
total depth, ft
3
permits on file
Mar 5, 2002
last permit issued
Mar 5, 2002
completed
7.97K
cumulative oil, bbl
31.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2001 THROUGH Mar 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 5, 2002
Shut in
—
Plugged
Jan 24, 2003

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Edwards C O-13-30003Dillard, W. (Caddo)Lane Operating Company17.31K31.2KMar 2002 – Mar 2003
Edwards C O-13-29975Clay County RegularLane Operating Company1661216Oct 2001 – Sep 2002

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. 1Lane Operating CompanyOct 2001 → Oct 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
518034-99RecompletionLane Operating CompanyMar 4, 2002Mar 5, 2002Mar 5, 20025,900
510221-98DrillLane Operating CompanyNov 8, 2001Jun 14, 2001Jun 23, 20016,700
510221-99DrillLane Operating CompanyJun 13, 2001Jun 14, 2001—6,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-29975————
—— O-13-30003————

Formation tops

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

FormationMD ftSubsea
BrysonBRYSON LIME4,327-3,157
CaddoCADDO LIME5,687-4,517
Ellenburger6,520-5,350

Perforations

Perforated and open-hole intervals.

FromToType
5,7085,724Perforated
5,7345,766Perforated
5,7865,794Perforated
6,4006,450Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62531012.25200 S
4.56,5757.875400 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
00May 3, 2002Mar 7, 2002Yes
00Mar 19, 2002——
00Feb 1, 2002Nov 7, 2001Yes
00Jan 15, 2002——

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