WELL · 42-415-35188 · DISTRICT 8

Bullard #7

Y

Scurry County · Revilo (Clear Fork) field · Producing  · Vertical

Bullard #7 (API 42-415-35188) is a well in Scurry County operated by Cml Exploration LLC, completed January 30, 2016 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 12, 2015, permitted to 4,000 ft.

Completion filings report 9 formation tops, including Yates, San Andres, Coleman Junction, Glorieta.

Its lease has reported 185K barrels of oil and 30 mcf of gas since June 2011, last reporting in July 2026. The lease carries 6 wells, so these are lease totals, not this well alone.

Operator of record

CML Exploration LLC

Based in
Austin, TX
P-5 status
Active (A)
P-5 last filed
Oct 20, 2025
Permits on file
514
Phone
(512) 328-8085

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCML Exploration LLC
Production reportsCML Exploration, LLCthrough Apr 2026
Latest permitCML Exploration, LLCNov 12, 2015
4,000
total depth, ft
1
permits on file
Nov 12, 2015
last permit issued
Jan 30, 2016
completed
185K
cumulative oil, bbl
30
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 30, 2016
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; they carry 6 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bullard O-11-69797Revilo (Clear Fork)CML Exploration, LLC6185K30Jun 2011 – Jul 2026

Oil, barrels lease total

Last 12 months 9,507 · prior 12 10,698(-11%)

05001K1.5K202420252026

Chain of custody

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

  1. 1WTP Energy, Inc.Oct 2011 → Jul 2014
  2. 2CML Exploration, LLCAug 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
811808-99DrillCML Exploration, LLCNov 9, 2015Nov 12, 2015Dec 4, 20154,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-69797————

Formation tops

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

FormationMD ftSubsea
YatesYATES - HIGH FLUIDS AND/OR GAS F7421,749
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO1,792699
Coleman JunctionCOLEMAN JUNCTION - POSSIBLE LOST2,096395
Glorieta2,576-85
Clear ForkCLEARFORK3,330-839
Fuller Sand——
Spraberry——
Wichita-AlbanyWICHITA——
Wichita-AlbanyWICHITA ALBANY - OVER PRESSURED——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
3,3923,416Perforated
3,4563,516Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62545912.25300 S
5.53,8907.875840 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
00Feb 25, 2016Feb 15, 2016Yes

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