WELL · 42-105-37234 · DISTRICT 7

Pierce V. I. #206

Y

Crockett County · Ozona (Canyon Sand) field · Producing  · Vertical

Pierce V. I. #206 (API 42-105-37234) is a well in Crockett County operated by Toc Energy Resources LLC, completed October 27, 1996 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 6, 1996, permitted to 6,900 ft.

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

Completion filings report 3 formation tops, including Clear Fork, Lm Marker, Canyon.

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

Operator of record

Toc Energy Resources LLC

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

Fort Worth, TX · P-5 Y, filed Dec 4, 2025 · 2 permits on file · (817) 874-8111

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleToc Energy Resources LLC
Production reportsToc Energy Resources, LLCthrough Mar 2026
Latest permitOjb, Inc.May 6, 1996

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

6,900
total depth, ft
1
permits on file
May 6, 1996
last permit issued
Oct 27, 1996
completed
0
cumulative oil, bbl
363K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1996 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 27, 1996
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Pierce, V. I. G-9-161125Ozona (Canyon Sand)Toc Energy Resources, LLC10363KOct 1996 – Jul 2026

Gas, mcf lease total

Last 12 months 1,360 · prior 12 1,859(-27%)

05001K202420252026

Chain of custody

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

  1. 1Ojb, Inc.Nov 1996 → Dec 2001
  2. 2Baker ResourcesJan 2002 → Jul 2020
  3. 3Toc Energy Resources, LLCFeb 2022 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
446163-99DrillOjb, Inc.Mar 21, 1996May 6, 1996Sep 8, 19966,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-161125————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK3,000-618
LM Marker5,850-3,468
CanyonCANYON SD5,930-3,548

Perforations

Perforated and open-hole intervals.

FromToType
6,3576,384Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,48711760 S
4.56,5857.875445 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
00Feb 14, 1997Dec 20, 1996Yes
00Jan 29, 1997——

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) and the University Lands library. 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/10537234, documented in the API reference.