TEXAS · WELLS · WISE COUNTY · CHARLES, F. R. LEASE · API 42-497-32733 · DISTRICT 7C

Charles F. R. #1

Plugged

Wise County · Morris (Consolidated Congl.) field  · Vertical

Charles F. R. #1 (API 42-497-32733) is a plugged well in Wise County, plugged August 19, 2002, last operated by Devon Energy Operating CO. L.P..

The RRC has issued 3 drilling permits between 1984 and 2002, permitted to 6,200 ft.

Completion filings report 2 formation tops, including Caddo, Atoka.

Its lease has reported 3.42K barrels of oil and 86.3K mcf of gas since January 1993, last reporting in November 2002.

Operator of record

Devon Energy Operating Co. L.P.

Based in
Oklahoma City, OK
P-5 status
Inactive (I)
P-5 last filed
Jun 29, 2011
Permits on file
939
Phone
(405) 235-3611

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDevon Energy Operating Co. L.P.
Production reportsDevon Energy Operating Co., L.P.through Jun 2002
Latest permitDevon Energy Operating Co., L.P.Aug 2, 2002
6,200
total depth, ft
3
permits on file
Aug 2, 2002
last permit issued
Mar 4, 1985
completed
3.42K
cumulative oil, bbl
86.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 4, 1985
Shut in
—
Plugged
Aug 19, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Charles, F. R. O-13-25325Morris (Consolidated Congl.)Devon Energy Operating Co., L.P.13.42K86.3KJan 1993 – Nov 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. 1Mitchell Energy CorporationJan 1993 → Dec 2000
  2. 2Mitchell Energy Company L.P.Jan 2001 → Dec 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
522470-99RecompletionDevon Energy Operating Co., L.P.Aug 2, 2002Aug 2, 2002—6,040
231760-99DrillMitchell Energy CorporationMay 13, 1985Mar 8, 1984—6,200
231759-99DrillMitchell Energy CorporationMar 6, 1984Mar 8, 1984Dec 17, 19846,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 4, 1985Charles F. R. O-13-25325Morris (Consolidated Congl.)Devon Energy Operating Co. L.P.Plugged—

Formation tops

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

FormationMD ftSubsea
CaddoCADDO LIME4,950-4,115
AtokaBASAL ATOKA5,925-5,090

Perforations

Perforated and open-hole intervals.

FromToType
5,0525,111Perforated
5,4615,610Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62528814.75280 S
4.56,0408.75450 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
00Apr 18, 1986Apr 4, 1986—
00Jun 11, 1985May 13, 1985—
00Jun 4, 1985——

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