TEXAS · WELLS · KING COUNTY · API 42-269-32601 · DISTRICT 7B
6666-Pitchfork Unit #5
King County · Legacy (Tannehill Sand) field · Producing · Vertical
6666-Pitchfork Unit #5 (API 42-269-32601) is a well in King County operated by Burnett Oil CO. Inc., completed November 4, 2005 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued October 7, 2005, permitted to 3,890 ft.
It was permitted by Cholla Petroleum, Inc. and has since transferred to Burnett Oil CO. Inc. on the wellbore schedule.
Completion filings report 2 formation tops, including Stockwether, Tannehill.
Its 2 leases have reported 790K barrels of oil since August 2005, last reporting volume in April 2026. The leases carry 36 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Cholla Petroleum, Inc.; the EWA schedule now lists a different operator.
- Based in
- Fort Worth, TX
- P-5 status
- Active (A)
- P-5 last filed
- Feb 5, 2026
- Permits on file
- 368
- Phone
- (817) 332-5108
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Burnett Oil Co. Inc. |
| Production reports | Burnett Oil Co., Inc.through Apr 2026 |
| Latest permit | Cholla Petroleum, Inc.Oct 7, 2005 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 3,890
- total depth, ft
- 1
- permits on file
- Oct 7, 2005
- last permit issued
- Nov 4, 2005
- completed
- 790K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2005 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Nov 4, 2005
- 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 2 leases this well is completed on; they carry 36 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| 6666-Pitchfork Unit O-11-71462 | Legacy (Tannehill Sand) | Burnett Oil Co., Inc. | 26 | 20.7K | 0 | Jul 2025 – Apr 2026 |
| Pitchfork O-11-68801 | Legacy (Tannehill Sand) | Burnett Oil Co., Inc. | 10 | 769K | 0 | Aug 2005 – Jun 2025 |
Oil, barrels lease total
Last 12 months 22,265 · prior 12 12,301(+81%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Cholla Petroleum, Inc.Sep 2005 → Nov 2024
- 2Burnett Oil Co., Inc.Dec 2024 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 607507-99 | Drill | Cholla Petroleum, Inc. | Oct 7, 2005 | Oct 7, 2005 | Oct 14, 2005 | 4,599 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Nov 4, 2005 | 6666-Pitchfork Unit O-11-71462 | Legacy (Tannehill Sand) | Burnett Oil Co. Inc. | Producing | 3,890 |
| Nov 4, 2005 | Pitchfork O-11-68801 | Legacy (Tannehill Sand) | Burnett Oil Co. Inc. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,064 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Stockwether | 3,802 | -1,738 |
| TannehillTANNEHILL LIME | 3,872 | -1,808 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,826 | 3,842 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 341 | 17.5 | 380 S |
| 8.625 | 887 | 12.25 | 150 S |
| 5.5 | 3,886 | 7.875 | 300 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jul 31, 2025 | Nov 21, 2005 | Yes |
| 00 | Feb 8, 2006 | Nov 21, 2005 | Yes |
| 00 | Dec 7, 2005 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Dec 31, 2008. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Stockwether, Tannehill | TIFF | 890 to 3,890 | Dec 31, 2008run Oct 21, 2005 | 1.71 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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.
- Wellbore filings for 42-269-32601 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-269-32601 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/26932601, documented in the API reference.