TEXAS · WELLS · CROCKETT COUNTY · ARCO-CHILDRESS LEASE · API 42-105-36888 · DISTRICT 6E

Arco-Childress #5

On schedule

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

Arco-Childress #5 (API 42-105-36888) is a permitted well in Crockett County filed by Union Pacific Resources Company; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 23, 1995, permitted to 6,422 ft.

It was permitted by Union Pacific Resources Company and has since transferred to Scout Energy Management LLC on the wellbore schedule.

Its lease has reported 23 barrels of oil and 881K mcf of gas since August 1995, last reporting volume in August 2026.

Operator of record

Scout Energy Management LLC

Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.

Based in
Dallas, TX
P-5 status
Active – Extension (X)RRC P-5 file of Oct 22, 2026
P-5 last filed
Oct 20, 2026
Permits on file
483
Phone
(972) 277-1397

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleScout Energy Management LLC
Production reportsScout Energy Management LLCthrough Aug 2026
Latest permitUnion Pacific Resources CompanyMay 23, 1995

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

6,422
total depth, ft
1
permits on file
May 23, 1995
last permit issued
—
completed
23
cumulative oil, bbl
881K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · AUG 1995 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
—
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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
Arco-Childress G-9-155520Ozona (Canyon Sand)Scout Energy Management LLC123881KAug 1995 – Aug 2026

Gas, mcf lease total

Last 12 months 289 · prior 12 5,231(-94%)

05001K1.5K202420252026

Wells named Arco-Childress

Scout Energy Management LLC's other wells filed under this lease name in Crockett County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Operator on the lease's P-4

Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.

OperatorFromTo
Scout Energy Management LLCJan 1, 2025today
Epic Permian Operating, LLCSep 1, 2016Jan 1, 2025
Anadarko E&P Onshore LLCJan 1, 2013Sep 1, 2016
Anadarko E&P Company LPDec 1, 2002Jan 1, 2013
Rme Petroleum CompanyFeb 1, 2001Dec 1, 2002
Union Pacific Resources CompanyOct 9, 1995Feb 1, 2001

Reporting production

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

  1. 1Union Pacific Resources CompanyAug 1995 → Jan 2001
  2. 2Rme Petroleum CompanyFeb 2001 → Nov 2002
  3. 3Anadarko E&P Company LPDec 2002 → Dec 2012
  4. 4Anadarko E&P Onshore LLCJan 2013 → Aug 2016
  5. 5Epic Permian Operating, LLCSep 2016 → Dec 2024
  6. 6Scout Energy Management LLCFeb 2025 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
434712-99DrillUnion Pacific Resources CompanyApr 10, 1995May 23, 1995Jul 6, 19957,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—Arco-Childress G-9-155520Ozona (Canyon Sand)Scout Energy Management LLCProducing6,422

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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Oct 9, 1995—Yes

Well logs

1 log loaded from the RRC's log index, the latest received Aug 22, 2008. Density, Neutron.

Click a log to get its files from the RRC (free account). It opens in a new tab on the RRC's log search for this well, which lists each file to view or download; the RRC has no address for a single file.

Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON/DENSITY POROSITYTIFF100 to 6,812Aug 22, 2008run Jul 14, 19951.97

These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/10536888, documented in the API reference.