WELL · 42-415-00635 · DISTRICT 8

Fred #1

Y

Scurry County · Paladin-Barton (Canyon) field · Injection  · Vertical

Fred #1 (API 42-415-00635) is a well in Scurry County operated by Raw Oil & Gas Inc., completed May 1, 1992 and listed as injection on the RRC schedule.

The RRC has issued one drilling permit, issued March 10, 1992, permitted to 6,700 ft.

It was permitted by Hat Oil & Gas, Inc. and has since transferred to Raw Oil & Gas Inc. on the wellbore schedule.

Completion filings report one formation top, including San Andres.

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

It holds an active disposal or injection permit, with 77.7K barrels injected in the 12 months reported through June 2025.

Operator of record

Raw Oil & Gas Inc.

Permitted by Hat Oil & Gas, Inc.; the EWA schedule now lists a different operator.

Lubbock, TX · P-5 Y, filed Nov 4, 2025 · 148 permits on file · (806) 239-3443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRaw Oil & Gas Inc.
Production reportsnone
Latest permitHat Oil & Gas, Inc.Mar 10, 1992

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
1
permits on file
Mar 10, 1992
last permit issued
May 1, 1992
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 1, 1992
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
Fred O-11-66856Paladin-Barton (Canyon)Raw Oil & Gas, Inc.100Jan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
396984-99ReenterHat Oil & Gas, Inc.Feb 26, 1992Mar 10, 1992Apr 29, 19926,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-66856————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
San Andres1,649

Perforations

Perforated and open-hole intervals.

FromToType
1,6496,700Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,649——

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
00Jun 10, 1992May 13, 1992—
00Jun 1, 1992——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

77.7K
bbl, last 12 reported months
5.89M
bbl, all reported
Jun 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000077929W-14 DisposalActive3,0008001,649–6,700

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 77,730 · prior 12 73,966(+5%)

05K10K20242025

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