WELL · 42-237-40568 · DISTRICT 13

Voyles #1D

N

Jack County  · Vertical

Voyles #1D (API 42-237-40568) is a permitted well in Jack County filed by G & F Oil, Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued February 27, 2020, permitted to 1,999 ft.

Operator of record

G & F Oil, Inc.

Aledo, TX · P-5 Y, filed Jul 4, 2026 · 150 permits on file · (817) 939-8851

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitG & F Oil, Inc.Feb 27, 2020
1,999
total depth, ft
1
permits on file
Feb 27, 2020
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

33.427097, -98.319112

OpenStreetMap → ·  Google Maps →

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

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
862295-99DrillG & F Oil, Inc.Feb 25, 2020Feb 27, 2020—1,999

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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Emard42-237-40645

0.8 KM · G & F Oil, Inc. · Section with this well →

Butram3,202-2,158
Bryson3,964-2,920
Caddo5,040-3,996
Atoka—
Weir—
Village Bend—
Strawn—
Palo Pinto—

10 TOPS · FIRST 8

Voyles M42-237-40620

0.9 KM · G & F Oil, Inc. · Section with this well →

Gunsight605470
Butram3,120-2,045
Bryson3,850-2,775
Caddo5,050-3,975
Strawn—
Atoka—
Weir—
Village Bend—

10 TOPS · FIRST 8

Montgomery42-237-40643

1.1 KM · G & F Oil, Inc. · Section with this well →

Caddo5,122-4,051
Butram—
Atoka—
Bryson—
Gunsight—
Palo Pinto—
Strawn—
Village Bend—

10 TOPS · FIRST 8

Montgomery42-237-40625

1.1 KM · G & F Oil, Inc. · Section with this well →

Bryson3,902-2,831
Caddo5,142-4,071
Weir—
Canyon—
Gunsight—
Palo Pinto—
Strawn—
Village Bend—

10 TOPS · FIRST 8

Rater West42-237-40451

1.4 KM · G & F Oil, Inc. · Section with this well →

Gunsight650348
Bryson3,390-2,392
Caddo5,160-4,162
Atoka—
Palo Pinto—
Canyon—
Butram—
Weir—

10 TOPS · FIRST 8

Emard42-237-40582

1.5 KM · G & F Oil, Inc. · Section with this well →

Strawn3,400-2,351
Caddo5,120-4,071
Conglomerate5,366-4,317
Marble Falls5,386-4,337
Barnett5,772-4,723
Ellenburger6,040-4,991
Village Bend—
Atoka—

14 TOPS · FIRST 8

Emard M42-237-40611

1.5 KM · G & F Oil, Inc. · Section with this well →

Bryson3,256-2,229
Caddo5,095-4,068
Gunsight—
Canyon—
Butram—
Strawn—
Palo Pinto—
Village Bend—

10 TOPS · FIRST 8

Briscoe42-237-40506

1.8 KM · Caribou Operating, Inc. · Section with this well →

Caddo5,100-4,104
Atoka—
Weir—
Village Bend—
Strawn—
Palo Pinto—
Gunsight—
Canyon—

10 TOPS · FIRST 8

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