TEXAS · WELLS · ATASCOSA COUNTY · API 42-013-01888 · DISTRICT 01
Pfeil O.H. #3
Atascosa County · Jourdanton (Buda) field · Temp Abandoned · Vertical
Pfeil O.H. #3 (API 42-013-01888) is a well in Atascosa County operated by Trailblazer Energy Resources LLC, completed November 7, 1995 and listed as temp abandoned on the RRC schedule, shut in August 1, 2024.
The RRC has issued 3 drilling permits (amended once) between 1985 and 1996, permitted to 7,410 ft.
It was permitted by Exxon Corp. and has since transferred to Trailblazer Energy Resources LLC on the wellbore schedule.
Completion filings report one formation top, including Edwards.
No lease production has been reported under this well’s leases.
Operator of record
Trailblazer Energy Resources LLC
Permitted by Exxon Corp.; the EWA schedule now lists a different operator.
- Based in
- Tulsa, OK
- P-5 status
- Active (A)
- P-5 last filed
- Oct 16, 2025
- Permits on file
- 30
- Phone
- (918) 728-3020
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Trailblazer Energy Resources LLC |
| Production reports | Trailblazer Energy Resources,llcthrough Jul 2024 |
| Latest permit | Exxon Corp.Jan 26, 1996 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,410
- total depth, ft
- 4
- permits on file
- Jan 26, 1996
- last permit issued
- Nov 7, 1995
- completed
- 0
- cumulative oil, bbl
- 392K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Nov 7, 1995
- Shut in
- Aug 1, 2024
- 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Pfeil, O.H. G-1-157543 | Jourdanton (Buda) | Trailblazer Energy Resources,llc | 1 | 0 | 305K | Nov 1995 – Jul 2026 |
| Pfeil, O. H. G-1-125830 | Jourdanton (Georgetown) | Exxon Corp. | 1 | 0 | 86.7K | Jan 1993 – Nov 1995 |
Gas, mcf lease total
Last 12 months 0 · prior 12 665(-100%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Exxon Corp.Jan 1993 → May 1999
- 2Wagner Oil CompanyJun 1999 → Nov 2002
- 3Virtex Petroleum Company, Inc.Dec 2002 → Jan 2008
- 4Virtex Operating Company, Inc.Feb 2008 → Aug 2023
- 5Trailblazer Energy Resources,llcSep 2023 → Jul 2024
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 444134-99 | Recompletion | Exxon Corp. | Jan 26, 1996 | Jan 26, 1996 | Oct 30, 1995 | 6,984 |
| 334472-98 | Recompletion | Exxon Corp. | Nov 4, 1987 | Aug 18, 1987 | — | 7,410 |
| 334472-99 | Recompletion | Exxon Corp. | Aug 13, 1987 | Aug 18, 1987 | — | 7,410 |
| 292376-99 | Recompletion | Exxon Corp. | Dec 6, 1985 | Dec 9, 1985 | — | 7,410 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Nov 7, 1995 | Pfeil O.H. G-1-157543 | Jourdanton (Buda) | Trailblazer Energy Resources LLC | Temp Abandoned · shut in Aug 1, 2024 | 7,410 |
| Oct 27, 1987 | Pfeil O. H. G-1-125830 | Jourdanton (Georgetown) | Exxon Corp. | Not on Schedule | — |
| Nov 15, 1972 | Pfeil O. H. G-1-53983 | Jourdanton | Exxon Corp. | Not on Schedule | — |
| — | Pfeil O. H. O-1-739 | Jourdanton | Exxon Corp. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 479 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| EdwardsEDWARDS LIME | 7,404 | -6,925 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,870 | 6,898 | Perforated |
| 6,900 | 6,934 | Perforated |
| 7,049 | 7,054 | Perforated |
| 7,061 | 7,073 | Perforated |
| 7,315 | 7,322 | Perforated |
| — | 7,410 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,599 | 13.75 | 800 S |
| 5.5 | 7,406 | 8.75 | 300 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | May 10, 1996 | Feb 7, 1996 | Yes |
| 00 | Apr 11, 1996 | — | — |
| 00 | Feb 9, 1988 | Nov 24, 1987 | Yes |
| 00 | Dec 18, 1987 | — | — |
| 00 | Jan 12, 1984 | — | — |
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.
- Wellbore filings for 42-013-01888 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-013-01888 → scanned completion filings
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
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- —
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000062681 | H-1 Injection | Canceled Jul 24, 1987 | 2,500 | 2,500 | 7,150–7,402 |
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/01301888, documented in the API reference.