WELL · 42-475-37232 · DISTRICT 8

Caprito 83 #304H

Y

Ward County · Phantom (Wolfcamp) field · Producing  · Horizontal

Caprito 83 #304H (API 42-475-37232) is a horizontal well in Ward County operated by Abraxas Petroleum Corporation, completed October 27, 2017 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 20, 2017, permitted to 11,500 ft.

Completion filings report 10 formation tops, including Delaware, Clear Fork, Glorieta, Holt.

Its lease has reported 478K barrels of oil and 1.25M mcf of gas since October 2017, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Abraxas Petroleum Corporation

San Antonio, TX · P-5 Y, filed Oct 4, 2025 · 582 permits on file · (800) 321-2000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAbraxas Petroleum Corporation
Production reportsAbraxas Petroleum Corporationthrough Apr 2026
Latest permitAbraxas Petroleum CorporationApr 20, 2017
11,500
total depth, ft
1
permits on file
Apr 20, 2017
last permit issued
Oct 27, 2017
completed
478K
cumulative oil, bbl
1.25M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 27, 2017
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Caprito 83 O-10-49754Phantom (Wolfcamp)Abraxas Petroleum Corporation2478K1.25MOct 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 12,859 · prior 12 21,609(-40%)

02K4K202420252026

Gas, mcf lease total

Last 12 months 36,713 · prior 12 66,433(-45%)

010K20K202420252026

Chain of custody

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

  1. 1Abraxas Petroleum CorporationOct 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
825404-99DrillAbraxas Petroleum CorporationApr 11, 2017Apr 20, 2017May 9, 201711,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-49754————

Formation tops

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

FormationMD ftSubsea
Delaware4,740-2,072
Clear ForkCLEARFORK——
Glorieta——
Holt——
Queen——
Rustler——
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO——
Seven Rivers——
Tubb——
Yates——

Perforations

Perforated and open-hole intervals.

FromToType
11,44516,265Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,45017.51,752 S
9.6254,71512.251,710 S
711,4058.75905 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
00Apr 17, 2018Feb 6, 2018Yes

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