WELL · 42-253-34146 · DISTRICT 7
Aspen-Newman #2
Jones County · Bullard (Flippen Lime) field · Vertical
Aspen-Newman #2 (API 42-253-34146) is a plugged well in Jones County, plugged August 6, 1996, last operated by Aspen Exploration Inc..
The RRC has issued one drilling permit (amended once), issued May 2, 1994, permitted to 3,000 ft.
Completion filings report one formation top, including Flippen.
Its lease has reported 236 barrels of oil since May 1994, last reporting in October 1996.
Operator of record
Houston, TX · P-5 Y, filed May 4, 2012 · 34 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Aspen Exploration Inc. |
| Production reports | Aspen Exploration, Inc.through Oct 1994 |
| Latest permit | Aspen Exploration, Inc.May 2, 1994 |
- 3,000
- total depth, ft
- 2
- permits on file
- May 2, 1994
- last permit issued
- May 10, 1994
- completed
- 236
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 1994 THROUGH Oct 1996
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 10, 1994
- Shut in
- —
- Plugged
- Aug 6, 1996
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 |
|---|---|---|---|---|---|---|
| Aspen-Newman O-8-27197 | Bullard (Flippen Lime) | Aspen Exploration, Inc. | 1 | 236 | 0 | May 1994 – Oct 1996 |
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.
- 1Aspen Exploration, Inc.May 1994 → Oct 1994
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 423475-98 | Drill | Aspen Exploration, Inc. | Jun 13, 1994 | May 2, 1994 | May 3, 1994 | 3,000 |
| 423475-99 | Drill | Aspen Exploration, Inc. | May 2, 1994 | May 2, 1994 | — | 3,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-27197 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,818 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Flippen | 2,569 | -751 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,570 | 2,574 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 150 | 12.25 | 120 S |
| 5.5 | 2,948 | 7.875 | 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jul 14, 1994 | Jun 10, 1994 | Yes |
| 00 | Jun 22, 1994 | — | — |
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-253-34146 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-253-34146 → 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/25334146, documented in the API reference.