TEXAS · WELLS · HIDALGO COUNTY · API 42-215-33274 · DISTRICT 04
Boston Texas Land & Trust #47
Hidalgo County · Wildcat field · Vertical
- Fields on the latest permit · any of 4
- Arrowhead Ranch (VKS 12,300) · Arrowhead Ranch (VKS 12600 FB-2) · Arrowhead Ranch (Vicks 13,200) · Javelina (Vicksburg Cons.)
- Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.
Boston Texas Land & Trust #47 (API 42-215-33274) is a plugged well in Hidalgo County, plugged June 24, 2005, permitted by Shell Western E&P, with no operator of record on the wellbore schedule.
The RRC has issued one drilling permit, issued November 5, 2004, permitted to 15,000 ft.
Permitted by
The RRC's wellbore file lists this well with no operator of record.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Shell Western E&PNov 5, 2004 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 15,000
- total depth, ft
- 1
- permits on file
- Nov 5, 2004
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Jun 24, 2005
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.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 553241-99 | Drill | Shell Western E&P | Nov 5, 2004 | Nov 5, 2004 | — | 15,000 |
Well logs
1 log loaded from the RRC's log index, the latest received Oct 1, 2008. Resistivity.
Click a log to get its files from the RRC (free account). It opens in a new tab on the RRC's log search for this well, which lists each file to view or download; the RRC has no address for a single file.
| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITY | TIFF | 2,484 to 13,322 | Oct 1, 2008run Jan 10, 2005 | 2.21 |
These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
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-215-33274 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-215-33274 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/21533274, documented in the API reference.