WELL · 42-025-33462 · DISTRICT 2
Grissom #7
Bee County · Cosden West (Wilcox 9500) field · Vertical
Grissom #7 (API 42-025-33462) is a plugged well in Bee County, plugged January 23, 2013, last operated by Tidal Petroleum Inc..
The RRC has issued one drilling permit, issued March 29, 2007, permitted to 10,000 ft.
Completion filings report 3 formation tops, including Pettis, Yegua, Queen City.
Operator of record
- Based in
- Schertz, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Jun 15, 2026
- Permits on file
- 256
- Phone
- (210) 945-9878
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Tidal Petroleum Inc. |
| Production reports | Tidal Petroleum, Inc.through Dec 2012 |
| Latest permit | Tidal Petroleum, Inc.Mar 29, 2007 |
- 10,000
- total depth, ft
- 1
- permits on file
- Mar 29, 2007
- last permit issued
- May 10, 2007
- completed
- 0
- cumulative oil, bbl
- 135K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2007 THROUGH Jul 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 10, 2007
- Shut in
- —
- Plugged
- Jan 23, 2013
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 |
|---|---|---|---|---|---|---|
| Grissom G-2-228110 | Cosden, West (Wilcox 9500) | Tidal Petroleum, Inc. | 1 | 0 | 135K | May 2007 – Jul 2013 |
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.
- 1Tidal Petroleum, Inc.May 2007 → Dec 2012
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 635626-99 | Drill | Tidal Petroleum, Inc. | Mar 21, 2007 | Mar 29, 2007 | Apr 1, 2007 | 10,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-228110 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 413 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Pettis | 3,158 | -2,745 |
| YeguaBASE OF YEGUA | 4,080 | -3,667 |
| Queen City | 5,608 | -5,195 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,082 | 9,084 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 2,500 | 14.75 | 800 S |
| 7.625 | 8,536 | 9.875 | 200 S |
| 4.5 | 9,481 | 6.75 | 230 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 24, 2007 | May 29, 2007 | Yes |
| 00 | Jul 18, 2007 | — | — |
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-025-33462 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-33462 → 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/02533462, documented in the API reference.