WELL · 42-083-32918 · DISTRICT 7

Bertrand O. C. A #3

Plugged

Coleman County · Glen Cove S. (Palo Pinto) field  · Vertical

Bertrand O. C. A #3 (API 42-083-32918) is a plugged well in Coleman County, plugged November 26, 2019, last operated by Imperator Operating LLC.

The RRC has issued one drilling permit, issued March 22, 1982, permitted to 3,800 ft.

It was permitted by Locker Petroleum and has since transferred to Imperator Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Gunsight, Serratt, Palo Pinto.

Operator of record

Imperator Operating LLC

Permitted by Locker Petroleum; the EWA schedule now lists a different operator.

Watauga, TX · P-5 Y, filed May 29, 2025 · (214) 566-0423

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleImperator Operating LLC
Production reportsOil, Gas, Etc. LLCthrough Oct 2017
Latest permitLocker PetroleumMar 22, 1982

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

3,800
total depth, ft
1
permits on file
Mar 22, 1982
last permit issued
Dec 7, 1982
completed
0
cumulative oil, bbl
38K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 7, 1982
Shut in
—
Plugged
Nov 26, 2019

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
Bertrand, O. C. "A" G-8-120867Glen Cove, S. (Palo Pinto)Imperator Operating, LLC1038KJan 1993 – Nov 2019

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. 1Coleman County ProjectJan 1993 → Sep 1996
  2. 2Subsurface Energy Corp.Jan 1997 → Dec 2001
  3. 3Rockwood Resources IncJan 2002 → Mar 2008
  4. 4Cedar Ridge Energy, Inc.Apr 2013 → Jun 2013
  5. 5Minuteman Energy, LLCDec 2013 → Dec 2013
  6. 6Oil, Gas, Etc. LLCJul 2017 → Oct 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
154077-99DrillLocker PetroleumMar 22, 1982Mar 22, 1982Sep 24, 19823,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-120867————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Gunsight2,160
Serratt2,403
Palo PintoUPPER PALO PINTO2,904
Palo PintoLOWER PALO PINTO3,218

Perforations

Perforated and open-hole intervals.

FromToType
3,2183,224Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521311165 S
2.37521311165 S
2.3753,190——
4.53,2966.75250 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 7, 1986Apr 15, 1986—
00May 6, 1986——
00Jan 12, 1984Dec 10, 1982—

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