TEXAS · WELLS · LA SALLE COUNTY · BROWN TRUST LEASE · API 42-283-35599 · DISTRICT 01
Brown Trust #32H
La Salle County · Eagleville (Eagle Ford-1) field · Producing · Horizontal
Brown Trust #32H (API 42-283-35599) is a horizontal well in La Salle County operated by Javelin Energy Partners Mgmt LLC, completed June 9, 2016 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued September 3, 2015, permitted to 9,038 ft.
It was permitted by Carrizo (Eagle Ford) LLC and has since transferred to Javelin Energy Partners Mgmt LLC on the wellbore schedule.
Completion filings report 10 formation tops, including Midway, Escondido, Olmos, Austin Chalk.
Its lease has reported 15.9M barrels of oil and 23.7M mcf of gas since January 2012, last reporting volume in August 2026. The lease carries 73 wells, so these are lease totals, not this well alone.
Operator of record
Javelin Energy Partners Mgmt LLC
Permitted by Carrizo (Eagle Ford) LLC; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Feb 24, 2026
- Permits on file
- 234
- Phone
- (469) 575-3800
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Javelin Energy Partners Mgmt LLC |
| Production reports | Javelin Energy Partners Mgmt LLCthrough Mar 2026 |
| Latest permit | Carrizo (Eagle Ford) LLCSep 3, 2015 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,038
- total depth, ft
- 2
- permits on file
- Sep 3, 2015
- last permit issued
- Jun 9, 2016
- completed
- 15.9M
- cumulative oil, bbl
- 23.7M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · APR 2012 THROUGH AUG 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 9, 2016
- Shut in
- —
- 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.
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.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 73 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Brown Trust O-1-15756 | Eagleville (Eagle Ford-1) | Javelin Energy Partners Mgmt LLC | 73 | 15.9M | 23.7M | Jan 2012 – Aug 2026 |
Oil, barrels lease total
Last 12 months 457,157 · prior 12 500,496(-9%)
Gas, mcf lease total
Last 12 months 621,257 · prior 12 770,739(-19%)
Wells named Brown Trust
Javelin Energy Partners Mgmt LLC's other wells filed under this lease name in La Salle County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1Carrizo (Eagle Ford) LLCApr 2012 → Jan 2020
- 2Callon (Eagle Ford) LLCFeb 2020 → Jun 2023
- 3Ridgemar Energy Operating, LLCJul 2023 → Jan 2025
- 4Javelin Energy Partners Mgmt LLCFeb 2025 → Aug 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 809894-98 | Drill | Carrizo (Eagle Ford) LLC | Feb 8, 2016 | Sep 3, 2015 | Apr 28, 2016 | 11,000 |
| 809894-99 | Drill | Carrizo (Eagle Ford) LLC | Aug 31, 2015 | Sep 3, 2015 | Feb 21, 2016 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 9, 2016 | Brown Trust O-1-15756 | Eagleville (Eagle Ford-1) | Javelin Energy Partners Mgmt LLC | Producing | 9,038 |
Formation tops
As filed on W-2/G-1. Subsea from 516 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Midway | 3,461 | -2,945 |
| Escondido | 5,758 | -5,242 |
| OlmosOLMOS - DISPOSAL | 6,790 | -6,274 |
| Austin Chalk | 8,257 | -7,741 |
| Eagle FordEAGLE FORD - H2S | 9,135 | -8,619 |
| BudaBUDA - H2S | — | — |
| Queen City | — | — |
| Sparta | — | — |
| WilcoxWILCOX - DISPOSAL | — | — |
| Yegua | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,470 | 17,821 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 3,930 | 13.5 | 1,995 S |
| 5.5 | 17,945 | 8.75 | 2,590 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 17, 2016 | Aug 3, 2016 | — |
| 00 | May 4, 2016 | Apr 29, 2016 | Yes |
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-283-35599 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-283-35599 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here 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/28335599, documented in the API reference.