WELL · 42-399-35540 · DISTRICT 7

Garey Ranch #2

Y

Runnels County · Hollow Creek (Dog Bend) field · Producing  · Vertical

Garey Ranch #2 (API 42-399-35540) is a well in Runnels County operated by Fossil Petroleum LLC, completed February 6, 2019 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued December 14, 2017, permitted to 4,000 ft.

Completion filings report 10 formation tops, including Coleman Junction, Serratt Sands, Home Creek, Dog Bend Lime.

Its lease has reported 305 barrels of oil and 28.5K mcf of gas since February 2019, last reporting in July 2026.

Operator of record

Fossil Petroleum LLC

San Angelo, TX · P-5 Y, filed Aug 4, 2025 · 24 permits on file · (325) 374-3575

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFossil Petroleum LLC
Production reportsFossil Petroleum LLCthrough Apr 2026
Latest permitFossil Petroleum LLCDec 14, 2017
4,000
total depth, ft
2
permits on file
Dec 14, 2017
last permit issued
Feb 6, 2019
completed
305
cumulative oil, bbl
28.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 6, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.722736, -99.758670

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Runnels County.

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
Garey Ranch O-9-20318Hollow Creek (Dog Bend)Fossil Petroleum LLC130528.5KFeb 2019 – Jul 2026

Gas, mcf lease total

Last 12 months 3,568 · prior 12 5,971(-40%)

05001K1.5K202420252026

Oil, barrels lease total

Last 12 months 17 · prior 12 18(-6%)

0510202420252026

Chain of custody

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

  1. 1Fossil Petroleum LLCMay 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
834034-98DrillFossil Petroleum LLCJan 3, 2019Dec 14, 2017—4,000
834034-99DrillFossil Petroleum LLCDec 7, 2017Dec 14, 2017Jan 31, 20194,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-20318————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - POSSIBLE WATE1,82049
Serratt Sands2,210-341
Home Creek2,460-591
Dog Bend Lime3,138-1,269
Cambrian——
Canyon——
Cisco——
King——
Problem Zone - 5 Mile Radius Aro——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
3,1383,161Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62522512.25150 S
4.53,5897.875610 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
00Aug 20, 2019Aug 5, 2019Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Garey Ranch42-399-35539

0.8 KM · Fossil Petroleum LLC · Section with this well →

Coleman Junction1,80061
Serratt Sands2,070-209
Home Creek2,430-569
Dog Bend Lime3,106-1,245
Goen Sand3,382-1,521
Jennings3,473-1,612
Gardner3,540-1,679
Canyon—

13 TOPS · FIRST 8

Leonard42-399-35340

3.4 KM · Revard Petroleum, L.L.C. · Section with this well →

Cook Sand1,645134
Serratt1,892-113
Home Creek2,218-439

Turner, M. E.42-083-36206

6.3 KM · Oil Projects, LLC · Section with this well →

Coleman Junction971
Tannehill1,380
Cook Sand - Disposal1,820
King Sand - Disposal1,992
Overall - Disposal2,470
Winchell Lime - Disposal2,520
Breneke Sand - Disposal—
Canyon—

10 TOPS · FIRST 8

Turner, M. E.42-083-36207

6.3 KM · Oil Projects, LLC · Section with this well →

Coleman Junction971
Tannehill1,380
Cook Sand - Disposal1,820
King Sand - Disposal1,992
Overall - Disposal2,470
Winchell Lime - Disposal2,520
Capps Lime - Disposal—
Crosscut Upper - Disposal—

10 TOPS · FIRST 8

Snelson42-399-34709

10.4 KM · Pioneer Energy Corporation · Section with this well →

Saxon (Seratt)2,010-45
Hag (Seratt)2,210-245
Leonard2,390-425
Leonard2,460-495
Leonard3,085-1,120
Saxon (Canyon Lime)3,177-1,212
Gardner3,524-1,559
Gardner Sand3,524-1,559

Snelson 242-399-34600

10.5 KM · Pioneer Energy Corporation · Section with this well →

Coleman Junction956908
Coleman Junction1,202662
Saddle Creek1,724140
Top Breckenridge LM1,936-72
Base Breckenridge LM1,972-108
Gunsight2,026-162
Jennings3,441-1,577
Gardner3,534-1,670

Snelson 442-399-34637

11.3 KM · Pioneer Energy Corporation · Section with this well →

Coleman Junction1,152739
Base Breckinridge Lime1,939-48
Base Breckenridge Lime1,939-48
Palo Pinto2,968-1,077
Palo Pinto2,968-1,077
Base Gardner Lime3,518-1,627

Wright 'A'42-399-35363

11.4 KM · Window Operating Co., The · Section with this well →

Upper Gardner Sand3,754-1,987
Upper Gray Sand3,829-2,062
Gray Sand3,927-2,160

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