WELL · 42-123-32110 · DISTRICT 2

Werland Robert E. et AL #1

Plugged

DE Witt County · Brushy Creek S. (Wilcox 13900) field  · Vertical

Werland Robert E. ET AL #1 (API 42-123-32110) is a plugged well in De Witt County, plugged July 25, 2014, last operated by Camden Resources LLC.

The RRC has issued 2 drilling permits between 2006 and 2007, permitted to 15,500 ft.

It was permitted by Camden Resources, Inc. and has since transferred to Camden Resources LLC on the wellbore schedule.

Operator of record

Camden Resources LLC

Permitted by Camden Resources, Inc.; the EWA schedule now lists a different operator.

Based in
Blanchard, OK
P-5 status
Inactive (I)
P-5 last filed
Oct 20, 2015
Permits on file
5
Phone
(405) 485-8200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCamden Resources LLC
Production reportsCamden Resources, LLCthrough May 2014
Latest permitCamden Resources, Inc.Oct 8, 2007

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

15,500
total depth, ft
2
permits on file
Oct 8, 2007
last permit issued
Dec 5, 2006
completed
0
cumulative oil, bbl
698K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH Jul 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 5, 2006
Shut in
—
Plugged
Jul 25, 2014

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
Werland, Robert E et AL G-2-241149Brushy Creek (Wilcox -S-1-11200)Camden Resources, LLC10671KOct 2007 – Jul 2014
Werland, Robert E. et AL G-2-227734Brushy Creek, S. (Wilcox 13900)Camden Resources, Inc.1026.9KApr 2007 – Oct 2007

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. 1Camden Resources, Inc.Apr 2007 → Aug 2007
  2. 2Camden Resources, LLCOct 2007 → May 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
646768-99RecompletionCamden Resources, Inc.Sep 26, 2007Oct 8, 2007Aug 1, 200714,432
623456-99DrillCamden Resources, Inc.Jul 28, 2006Jul 31, 2006Aug 17, 200615,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-227734————
—— G-2-241149————

Perforations

Perforated and open-hole intervals.

FromToType
10,95610,976Perforated
14,08814,122Perforated
14,20814,242Perforated
14,25414,262Perforated
14,28414,338Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,52617.52,110 S
9.62510,59512.25485 S
3.514,4326.5295 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 27, 2009Sep 17, 2008Yes
00Oct 27, 2008——
00Jul 13, 2007May 4, 2007Yes
00Jul 9, 2007——

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