WELL · 42-239-33475 · DISTRICT 2
Slazenger Frio #1
Jackson County · Morales (3260) field · Vertical
Slazenger Frio #1 (API 42-239-33475) is a plugged well in Jackson County, plugged December 14, 2012, last operated by Bnp Petroleum Corporation.
The RRC has issued one drilling permit (amended once), issued August 12, 2008, permitted to 4,500 ft.
Completion filings report one formation top, including Cordell Sand.
Operator of record
Corpus Chrsti, TX · P-5 Y, filed Jan 4, 2026 · 132 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | BNP Petroleum Corporation |
| Production reports | BNP Petroleum Corporationthrough Jul 2009 |
| Latest permit | BNP Petroleum CorporationSep 22, 2008 |
- 4,500
- total depth, ft
- 2
- permits on file
- Sep 22, 2008
- last permit issued
- Oct 1, 2008
- completed
- 0
- cumulative oil, bbl
- 45.8K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2008 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 1, 2008
- Shut in
- —
- Plugged
- Dec 14, 2012
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Slazenger Frio G-2-250785 | Morales (3260) | BNP Petroleum Corporation | 1 | 0 | 45.8K | Oct 2008 – Jul 2026 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1BNP Petroleum CorporationJan 2009 → Jul 2009
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 665952-98 | Drill | BNP Petroleum Corporation | Sep 4, 2008 | Sep 22, 2008 | Sep 24, 2008 | 4,500 |
| 665952-99 | Drill | BNP Petroleum Corporation | Jul 2, 2008 | Aug 12, 2008 | — | 4,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-250785 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 117 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Cordell Sand | 2,600 | -2,483 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,000 | 3,005 | Perforated |
| 3,321 | 3,330 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 774 | 12.25 | 320 S |
| 2.875 | 4,102 | 7.875 | 1,030 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 | Jun 15, 2015 | Jul 27, 2009 | Yes |
| 00 | Sep 10, 2009 | — | — |
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-239-33475 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-239-33475 → 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.
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/23933475, documented in the API reference.