TEXAS · WELLS · PALO PINTO COUNTY · ORME,CHARLSIE LEASE · API 42-363-32962 · DISTRICT 6E

Orme Charlsie #2

Y

Palo Pinto County · Belding (Bend Congl.) field · Producing  · Vertical

Orme Charlsie #2 (API 42-363-32962) is a well in Palo Pinto County operated by Cooper Oil & Gas LLC, completed January 24, 1994 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 1982 and 1994, permitted to 4,347 ft.

It was permitted by Echo Production, Inc. and has since transferred to Cooper Oil & Gas LLC on the wellbore schedule.

Completion filings report one formation top, including Conglomerate.

No lease production has been reported under this well’s leases.

Operator of record

Cooper Oil & Gas LLC

Permitted by Echo Production, Inc.; the EWA schedule now lists a different operator.

Based in
Fort Worth, TX
P-5 status
Active (A)
P-5 last filed
Mar 12, 2026
Permits on file
157
Phone
(817) 332-7755

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsCooper Oil & Gas, LLCthrough Apr 2026
Latest permitEcho Production, Inc.Feb 25, 1994
4,347
total depth, ft
2
permits on file
Feb 25, 1994
last permit issued
Jan 24, 1994
completed
0
cumulative oil, bbl
411K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 24, 1994
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Orme,charlsie G-8-107039Belding (Bend Congl.)Cooper Oil & Gas, LLC10411KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 5,542 · prior 12 6,831(-19%)

05001K202420252026

Chain of custody

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

  1. 1Echo Production, Inc.Jan 1994 → Feb 2025
  2. 2Cooper Oil & Gas, LLCMar 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
421111-99RecompletionEcho Production, Inc.Feb 14, 1994Feb 25, 1994—3,855
169437-99DrillEcho Production, Inc.Aug 17, 1982Aug 17, 1982—4,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 24, 1994Orme Charlsie G-8-107039Belding (Bend Congl.)Cooper Oil & Gas LLCProducing4,347

Formation tops

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

FormationMD ftSubsea
Conglomerate3,826-2,466

Perforations

Perforated and open-hole intervals.

FromToType
3,8263,830Perforated
4,1884,202Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62511812.2575 S
4.53,8447.87575 S
24,144——
4.54,3357.875100 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
00Mar 28, 1994Feb 14, 1994—
00Jan 12, 1984Sep 6, 1983—

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