TEXAS · WELLS · HIDALGO COUNTY · API 42-215-33276 · DISTRICT 04

Boston Texas Land & Trust #48

Shut in

Hidalgo County · Javelina ( 5 400) field · Temp Abandoned  · Vertical

Boston Texas Land & Trust #48 (API 42-215-33276) is a well in Hidalgo County operated by Merit Energy Company, completed August 27, 2012 and listed as temp abandoned on the RRC schedule, shut in September 1, 2012.

The RRC has issued 3 drilling permits (amended twice) between 2004 and 2012, permitted to 16,000 ft.

It was permitted by Oxy USA Inc. and has since transferred to Merit Energy Company on the wellbore schedule.

Completion filings report one formation top, including Vicksburg.

Its 2 leases have reported 154 barrels of oil and 64.6K mcf of gas since March 2005, with no volume in the three years through April 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Merit Energy Company

Permitted by OXY USA Inc.; the EWA schedule now lists a different operator.

Based in
Dallas, TX
P-5 status
Active (A)
P-5 last filed
Nov 7, 2025
Permits on file
1,049
Phone
(972) 701-8377

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMerit Energy Company
Production reportsOXY USA Inc.through Jul 2006
Latest permitOXY USA Inc.Jul 3, 2012

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

16,000
total depth, ft
5
permits on file
Jul 3, 2012
last permit issued
Aug 27, 2012
completed
154
cumulative oil, bbl
64.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2005 THROUGH Jul 2006

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 27, 2012
Shut in
Sep 1, 2012
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Boston Texas Land & Trust G-4-209829Javelina (Vicksburg Cons.)OXY USA Inc.115464.6KMar 2005 – Jul 2006
Boston Texas Land & Trust G-4-268882Javelina ( 5,400)Merit Energy Company100Aug 2012 – —

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.

  1. 1Shell Western E&PMar 2005 → Jul 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
743466-98RecompletionOXY USA Inc.Sep 19, 2012Jul 3, 2012Aug 20, 201216,000
743466-99RecompletionOXY USA Inc.Jun 25, 2012Jul 3, 2012—16,000
646750-99RecompletionShell Western E&PSep 26, 2007Oct 1, 2007—16,000
553819-98DrillShell Western E&PJan 11, 2005Nov 18, 2004Dec 10, 200417,000
553819-99DrillShell Western E&PNov 18, 2004Nov 18, 2004—15,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 27, 2012Boston Texas Land & Trust G-4-268882Javelina ( 5 400)Merit Energy CompanyTemp Abandoned · shut in Sep 1, 201216,000
Dec 29, 2010Boston Texas Land & Trust G-4-209829Javelina (Vicksburg Cons.)OXY USA Inc.Not on Schedule—

Formation tops

As filed on W-2/G-1. Subsea from 356 ft elevation.Download CSV →

FormationMD ftSubsea
VicksburgVICKSBURG T8,450-8,094
VicksburgVICKSBURG U9,663-9,307

Perforations

Perforated and open-hole intervals.

FromToType
5,5645,570Perforated
10,47610,488Perforated
12,18212,192Perforated
12,21012,214Perforated
12,22612,230Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,19817.51,523 S
12.256,96012.251,025 S
9.6256,96012.251,025 S
3.512,8006.51,312 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jul 25, 2013Oct 8, 2012—
00Feb 23, 2011Jan 26, 2011—
00May 30, 2006Oct 17, 2005—
00Oct 19, 2005Apr 13, 2005Yes
00Aug 5, 2005——

Well logs

1 log loaded from the RRC's log index, the latest received Jun 24, 2008. Gamma ray, Resistivity. 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.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
ResistivitySLIM EXTREME ARRAY INDUCTION GAMMA RAY FIANL COMPOSITESpans VicksburgTIFF14,150 to 14,676Jun 24, 2008run Jan 19, 2005—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

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/21533276, documented in the API reference.