TEXAS · WELLS · DIMMIT COUNTY · BRISCOE CHIP EAST RANCH LEASE · API 42-127-36184 · DISTRICT 01

Briscoe Chip East Ranch #27H

Y

Dimmit County · Briscoe Ranch (Eagleford) field · Producing  · Horizontal

Briscoe Chip East Ranch #27H (API 42-127-36184) is a horizontal well in Dimmit County operated by Javelin Energy Partners Mgmt LLC, completed October 28, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued March 19, 2014, permitted to 8,018 ft.

It was permitted by Anadarko E&P Onshore LLC and has since transferred to Javelin Energy Partners Mgmt LLC on the wellbore schedule.

Completion filings report 12 formation tops, including Midway, Escondido, Olmos, San Miguel.

Its lease has reported 244K barrels of oil and 1.56M mcf of gas since May 2014, last reporting volume in April 2026.

Operator of record

Javelin Energy Partners Mgmt LLC

Permitted by Anadarko E&P Onshore 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 scheduleJavelin Energy Partners Mgmt LLC
Production reportsJavelin Energy Partners Mgmt LLCthrough Apr 2026
Latest permitAnadarko E&P Onshore LLCMar 19, 2014

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

8,018
total depth, ft
2
permits on file
Mar 19, 2014
last permit issued
Oct 28, 2014
completed
244K
cumulative oil, bbl
1.56M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2014 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 28, 2014
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.

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Briscoe Chip East Ranch G-1-274413Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLC1244K1.56MMay 2014 – Apr 2026

Gas, mcf lease total

Last 12 months 40,880 · prior 12 50,944(-20%)

02K4K6K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Anadarko E&P Onshore LLCOct 2014 → Feb 2017
  2. 2SN EF Maverick, LLCMar 2017 → Aug 2023
  3. 3Javelin Energy Partners Mgmt LLCSep 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
780302-98DrillAnadarko E&P Onshore LLCApr 1, 2014Mar 19, 2014Aug 30, 20148,550
780302-99DrillAnadarko E&P Onshore LLCFeb 20, 2014Mar 19, 2014Apr 1, 20148,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 28, 2014Briscoe Chip East Ranch G-1-274413Briscoe Ranch (Eagleford)Javelin Energy Partners Mgmt LLCProducing8,018

Formation tops

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

FormationMD ftSubsea
Midway2,800-2,186
Escondido3,443-2,829
EscondidoESCONDIDO - DISPOSAL3,443-2,829
Olmos4,734-4,120
OlmosOLMOS - DISPOSAL4,734-4,120
San Miguel5,809-5,195
San MiguelSAN MIGUEL - H2S5,809-5,195
Pecan Gap6,885-6,271
Ausitn Chalk7,245-6,631
Austin Chalk7,245-6,631
Austin ChalkAUSTIN CHALK - H2S7,245-6,631
Eagle FordEAGLEFORD7,736-7,122
Eagle FordEAGLE FORD - H2S7,736-7,122
EdwardsEDWARDS - H2S——
GeorgetownGEORGETOWN - H2S——
Glen RoseGLEN ROSE - DISPOSAL——
Pearsall——

Perforations

Perforated and open-hole intervals.

FromToType
8,91213,798Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,01112.25677 S
5.513,8958.52,064 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
00Aug 14, 2024Jul 20, 2024—
00May 18, 2015Jan 19, 2015Yes
00Mar 3, 2015Oct 20, 2014Yes
00Nov 4, 2014Jul 15, 2014Yes

Well logs

1 log loaded from the RRC's log index, the latest received May 26, 2017. 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
RESISTIVITYSpans Pecan Gap, Ausitn Chalk, Austin Chalk, Eagle FordTIFF7,050 to 13,895May 26, 2017run May 3, 20140.31

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