WELL · 42-127-37345 · DISTRICT 1

Cochina SWD #2

WaterN

Dimmit County  · Vertical

Cochina Swd #2 (API 42-127-37345) is a disposal or injection well in Dimmit County operated by Choya Operating, LLC under an active UIC permit.

The RRC has issued 2 drilling permits between 2014 and 2016, permitted to 10,000 ft.

Completion filings report 9 formation tops, including Olmos, San Miguel, Austin Chalk, Eagle Ford.

It holds an active disposal or injection permit, with 2.41M barrels injected in the 12 months reported through March 2026.

Operator of record

Choya Operating, LLC

Austin, TX · P-5 Y, filed Jan 4, 2026 · 17 permits on file · (303) 597-5652

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitChoya Operating, LLCOct 27, 2016
10,000
total depth, ft
2
permits on file
Oct 27, 2016
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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
Cochina SWD O-1-19028Briscoe Ranch (Eagleford)Choya Operating, LLC100Apr 2017 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
819524-99DrillChoya Operating, LLCOct 18, 2016Oct 27, 2016Jan 6, 201710,000
796469-99DrillChoya Operating, LLCSep 17, 2014Oct 1, 2014—10,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-19028————

Formation tops

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

FormationMD ftSubsea
OlmosOLMOS - DISPOSAL3,580-3,088
San MiguelSAN MIGUEL - H2S4,730-4,238
Austin ChalkAUSTIN CHALK - H2S6,840-6,348
Eagle FordEAGLE FORD - H2S7,350-6,858
GeorgetownGEORGETOWN - H2S7,770-7,278
EdwardsEDWARDS - H2S8,102-7,610
Glen RoseGLEN ROSE - DISPOSAL8,560-8,068
EscondidoESCONDIDO - DISPOSAL——
Pearsall——

Perforations

Perforated and open-hole intervals.

FromToType
8,40010,000Open hole
8,4309,994Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,14714.751,638 S
78,4309.8751,060 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 13, 2023Aug 9, 2022—
00Mar 16, 2018Jul 10, 2017—
00Aug 31, 2017——

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.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

2.41M
bbl, last 12 reported months
21M
bbl, all reported
Mar 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000112474W-14 DisposalActive25,0004,2008,400–10,000

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 2,408,930 · prior 12 1,445,509(+67%)

0200K400K600K20252026

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