WELL · 42-163-33645 · DISTRICT 1

Casey Frio D #1H

Y

Frio County · Pearsall (Austin Chalk) field · NO Production  · Horizontal

Casey Frio D #1H (API 42-163-33645) is a horizontal well in Frio County operated by Mosaic Texas LLC, completed October 9, 2012 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit, issued August 21, 2012, permitted to 6,000 ft.

It was permitted by Ricochet Energy, Inc. and has since transferred to Mosaic Texas LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Anacacho, Ausitn Chalk, Austin Chalk.

Its lease has reported 47.1K barrels of oil since October 2012, last reporting in July 2026.

Operator of record

Mosaic Texas LLC

Permitted by Ricochet Energy, Inc.; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed May 4, 2026 · (432) 250-0250

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMosaic Texas LLC
Production reportsMosaic Exploration Operating LLCthrough Feb 2018
Latest permitRicochet Energy, Inc.Aug 21, 2012

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

6,000
total depth, ft
1
permits on file
Aug 21, 2012
last permit issued
Oct 9, 2012
completed
47.1K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 9, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Casey Frio D O-1-17593Pearsall (Austin Chalk)Mosaic Texas LLC147.1K0Oct 2012 – Jul 2026

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. 1Ricochet Energy, Inc.Oct 2012 → Jun 2014
  2. 2Baron Energy Inc.Jul 2014 → Aug 2015
  3. 3Ogog Operating, LLCOct 2015 → May 2017
  4. 4Mosaic Exploration Operating LLCNov 2017 → Feb 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
746601-99DrillRicochet Energy, Inc.Aug 16, 2012Aug 21, 2012Aug 30, 20126,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-17593————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
AnacachoTOP ANACACHO5,035
Ausitn Chalk5,345
Austin ChalkAUSTIN CHALK B-15,400

Perforations

Perforated and open-hole intervals.

FromToType
5,07010,650Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7578014.75465 S
7.6255,0709.8751,020 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
00Jun 16, 2014Mar 20, 2013Yes

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.

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