TEXAS · WELLS · BRAZOS COUNTY · RAE LEASE · API 42-041-32290 · DISTRICT 05

Rae #2H

Shut in

Brazos County · Aguila Vado (Eagleford) field · Shut In  · Horizontal

Rae #2H (API 42-041-32290) is a horizontal well in Brazos County operated by Wildfire Energy Operating LLC, completed November 14, 2014 and listed as shut in on the RRC schedule, shut in December 1, 2014.

The RRC has issued one drilling permit, issued May 31, 2014, permitted to 11,252 ft.

It was permitted by Apache Corporation and has since transferred to Wildfire Energy Operating LLC on the wellbore schedule.

Completion filings report 8 formation tops, including Wilcox, Austin Chalk, Navarro, Buda.

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

Operator of record

Wildfire Energy Operating LLC

Permitted by Apache Corporation; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Nov 24, 2025
Permits on file
171
Phone
(832) 558-0100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWildfire Energy Operating LLC
Production reportsnone
Latest permitApache CorporationMay 31, 2014

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

11,252
total depth, ft
1
permits on file
May 31, 2014
last permit issued
Nov 14, 2014
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 14, 2014
Shut in
Dec 1, 2014
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rae O-5-4197Aguila Vado (Eagleford)Wildfire Energy Operating LLC400Nov 2014 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
785733-99DrillApache CorporationApr 29, 2014May 31, 2014Jul 20, 201412,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 14, 2014Rae O-5-4197Aguila Vado (Eagleford)Wildfire Energy Operating LLCShut In · shut in Dec 1, 201411,252

Formation tops

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

FormationMD ft
WilcoxWILCOX - DISPOSAL3,610
Austin ChalkAUSTIN CHALK - LOST CIRCULATION7,100
NavarroNAVARRO - DISPOSAL7,140
BudaBUDA - PRODUCTION—
EdwardsEDWARDS - DISPOSAL—
GeorgetownGEORGETOWN - PRODUCTION—
SpartaSPARTA - DISPOSAL—
WoodbineWOODBINE - PRODUCTION—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,01213.51,400 S
9.62510,42612.251,270 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
00Dec 8, 2016Aug 3, 2016Yes

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.

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