WELL · 42-495-33539 · DISTRICT 8

Campbell #1

N

Winkler County · Keystone South (Wichita Albany) field  · Vertical

Campbell #1 (API 42-495-33539) is a well in Winkler County operated by Boyd & Mcwilliams Operating LLC, completed February 27, 2014.

The RRC has issued 2 drilling permits between 2013 and 2014, permitted to 7,900 ft.

Completion filings report 4 formation tops, including Glorieta, Clear Fork, Wichita-Albany, Wolfcamp.

Its 2 leases have reported 80.9K barrels of oil and 198K mcf of gas since February 2014, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Boyd & McWilliams Operating LLC

Midland, TX · P-5 Y, filed Jul 4, 2026 · 128 permits on file · (432) 559-4619

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBoyd & McWilliams Operating LLC
Production reportsBoyd & McWilliams Operating, LLCthrough Mar 2021
Latest permitBoyd & McWilliams Operating, LLCDec 3, 2014
7,900
total depth, ft
2
permits on file
Dec 3, 2014
last permit issued
Feb 27, 2014
completed
80.9K
cumulative oil, bbl
198K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 27, 2014
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Campbell O-10-48182Keystone, SouthFormentera Operations LLC179.5K198KMar 2014 – Jul 2026
Campbell O-10-44883Keystone, South (Wichita Albany)Boyd & McWilliams Operating, LLC11.42K0Feb 2014 – May 2017

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. 1Boyd & McWilliams Operating, LLCMar 2014 → Feb 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
800831-99RecompletionBoyd & McWilliams Operating, LLCNov 24, 2014Dec 3, 2014—7,900
774534-99DrillBoyd & McWilliams Operating, LLCNov 25, 2013Dec 6, 2013Dec 11, 20137,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-44883————
—— O-10-48182————

Formation tops

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

FormationMD ftSubsea
GlorietaGLORIETTA4,880-1,982
Clear ForkCLEARFORK5,130-2,232
Wichita-AlbanyWICHITA ALBANY6,330-3,432
Wolfcamp7,190-4,292

Perforations

Perforated and open-hole intervals.

FromToType
6,8927,068Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37563017.5675 S
8.6251,27211155 S
5.57,3987.8751,200 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 31, 2017Apr 7, 2014Yes
00Aug 5, 2014Apr 7, 2014Yes

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) and the University Lands library. 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/49533539, documented in the API reference.