WELL · 42-365-34236 · DISTRICT 6

Werner-Caraway #3

N

Panola County · Carthage (Page) field  · Vertical

Werner-Caraway #3 (API 42-365-34236) is a well in Panola County operated by O Benco Inc., completed December 9, 1999.

The RRC has issued 2 drilling permits (amended once) between 1999 and 2011, permitted to 6,300 ft.

Completion filings report 5 formation tops, including Fredericksburg, Fredricksburg, Paluxy, Rodessa.

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

Operator of record

O Benco Inc.

Based in
Shreveport, LA
P-5 status
Inactive (I)
P-5 last filed
May 9, 2019
Permits on file
374
Phone
(318) 865-8568

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleO Benco Inc.
Production reportsProline Energy Resources Incthrough Apr 2026
Latest permitO'Benco, Inc.Oct 10, 2011

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

6,300
total depth, ft
3
permits on file
Oct 10, 2011
last permit issued
Dec 9, 1999
completed
0
cumulative oil, bbl
577K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 9, 1999
Shut in
—
Plugged
—

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
Werner-Caraway G-6-266002Carthage (Paluxy)Proline Energy Resources Inc10370KJan 2012 – Jul 2026
Werner-Caraway G-6-176203Carthage (Page)O'Benco, Inc.10207KDec 1999 – May 2021

Gas, mcf lease total

Last 12 months 5,105 · prior 12 6,040(-15%)

01K2K202420252026

Chain of custody

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

  1. 1O'Benco, Inc.Dec 1999 → Aug 2016
  2. 2Proline Energy Resources IncSep 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
725431-99RecompletionO'Benco, Inc.Sep 30, 2011Oct 10, 2011Jan 4, 20126,300
488719-98DrillO'Benco, Inc.Feb 14, 2000Nov 5, 1999—6,300
488719-99DrillO'Benco, Inc.Oct 21, 1999Nov 5, 1999Nov 16, 19996,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-176203————
—— G-6-266002————

Formation tops

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

FormationMD ftSubsea
Fredericksburg2,504-2,317
Fredricksburg2,504-2,317
Paluxy2,964-2,777
Rodessa4,944-4,757
Pettit5,712-5,525

Perforations

Perforated and open-hole intervals.

FromToType
2,9642,970Perforated
6,1326,142Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62570711228 S
4.56,3107.8751,130 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
00Jan 31, 2013Apr 20, 2012—
00Apr 11, 2000Jan 18, 2000Yes
00Mar 28, 2000——

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