WELL · 42-105-34566 · DISTRICT 7

Pierce-State 106 #1

N

Crockett County · Ozona (Canyon Sand) field  · Vertical

Pierce-State 106 #1 (API 42-105-34566) is a well in Crockett County operated by Questa Oil & Gas CO., completed September 6, 1983.

The RRC has issued 2 drilling permits between 1983 and 1997, permitted to 6,700 ft.

Completion filings report 5 formation tops, including Clfk, Sprby, Wlfcmp, Friend Lm..

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

Operator of record

Questa Oil & Gas Co.

Tulsa, OK · P-5 Y, filed Sep 14, 2001 · 198 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleQuesta Oil & Gas Co.
Production reportsEpic Permian Operating, LLCthrough Feb 2022
Latest permitQuesta Oil & Gas Co.Oct 8, 1997

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

6,700
total depth, ft
2
permits on file
Oct 8, 1997
last permit issued
Sep 6, 1983
completed
0
cumulative oil, bbl
217K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 6, 1983
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
Pierce-State 106 G-9-165086V. I. P. (Clear Fork)Scout Energy Management LLC10124KSep 1997 – Jul 2026
Pierce-State "106" G-9-107404Ozona (Canyon Sand)Questa Oil & Gas Co.1092.2KJan 1993 – Sep 1997

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. 1Questa Oil & Gas Co.Jan 1993 → Jul 2001
  2. 2Unit Petroleum CompanyAug 2001 → Feb 2018
  3. 3Epic Permian Operating, LLCMar 2018 → Feb 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
468259-99RecompletionQuesta Oil & Gas Co.Oct 1, 1997Oct 8, 1997Aug 27, 19973,000
204778-99DrillQuesta Oil & Gas Co.Aug 6, 1983Aug 6, 1983—6,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-107404————
—— G-9-165086————

Formation tops

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

FormationMD ftSubsea
Clfk2,082215
Sprby3,525-1,228
Wlfcmp3,900-1,603
Friend Lm.5,000-2,703
CanyonCANYON SD.5,618-3,321

Perforations

Perforated and open-hole intervals.

FromToType
2,2252,270Perforated
5,9575,992Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,34311450 S
2.3755,921——
4.56,5557.875450 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
00Nov 24, 1997Oct 21, 1997Yes
00Nov 6, 1997——
00Jan 12, 1984Oct 3, 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) 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/10534566, documented in the API reference.