Skip to content

Abilene power: what the permit changes establish

Sample research memo · Longhorn Data Center / Crusoe Stargate Abilene. A dated example of the work a scoped monitoring pilot delivers.

Open this revision in the project change log.

The January 2025 amendment changes the permitted turbine configuration to five LM2500 units and five Titan 350 units, totaling 360.5 site-rated MW. The later O4721 issuance adds a documented federal operating-permit milestone. Neither record establishes current metered output or an open equipment procurement.

Record reviewed
October 27, 2026
Location
Taylor County, Texas
Applicant in the air record
Abilene DC 1, LLC
Purpose of this sample
Demonstrate evidence and change interpretation

This is a retrospective demonstration using the existing reviewed public record. It is not a paid client case, a new discovery on October 27 or a finding that every permitted unit is operating.

What changed in the record?

Changes described in the January 2025 modification technical review
FieldEarlier configuration described by the reviewModified configuration
Titan 350 count65
Titan 350 site ratingReview describes an increase; earlier rating not reproduced here38 MW per unit
LM2500 count65
LM2500 site ratingReview describes a reduction; earlier rating not reproduced here34.1 MW per unit
LM2500 annual permitted hours5,8808,760

The modification was received January 11, 2025 and approved January 22. It is a later filing under registration 177263. The original registration review records a receipt date of August 15, 2024; using January 11 as the first-ever filing would move the start of the timeline.

The later O4721 federal operating permit was issued January 16, 2026. Its issuance should be kept as a separate regulatory event. It does not replace the need for current operating evidence.

What is confirmed, and on what basis?

FindingEvidenceBoundary
360.5 MW turbine cohort5 × 34.1 MW + 5 × 38 MW in the 177263 modification reviewPermitted site ratings, not current net delivery to IT load
Onsite computing purposeThe same review describes onsite data-center and computing usePurpose stated in the document, not an observed dispatch profile
Federal operating permit issuedO4721, January 16, 2026Issued authorization, not proof of each unit's current operation
Data center live by an operator reportCrusoe announcement, September 30, 2025Operation by that report; exact first BTM generation day not established

What does this mean for a supplier or consultant?

Research interpretation: use the amended five-plus-five configuration when describing this permitted cohort. Preserve the earlier six-plus-six description as history. Combining both versions as separate equipment would overstate the documented fleet.

The longer LM2500 permitted-hours envelope changes the authorization described by the review. It does not establish annual run hours, availability, capacity factor or service demand. Those commercial and operating assumptions need their own evidence.

The legal-entity and site-name match is useful for following later filings: the permit uses Abilene DC 1 / Longhorn, while the project is commonly discussed as Crusoe Stargate Abilene. The record does not establish an unawarded order or identify a supplier opportunity that is currently available.

What remains unknown?

What would the next research check cover?

  1. Look for later records under the matched entity, site, registration and permit identifiers; record the date and result of the check.
  2. Compare the scope of any later filing with the existing cohort before treating it as additional equipment.
  3. Seek dated commissioning or operating evidence for claims about current configuration or output.
  4. Validate commercial participants and available scope directly before qualifying a sales opportunity.

These are proposed follow-up checks, not claims that a new filing or contract exists. Automated TCEQ retrieval currently has access limits; a pilot must agree a workable source-review route rather than promise uninterrupted coverage.

Source trail and reproducibility

Why do the document and review dates differ?

The documents describe events in 2024–2026. October 27, 2026 is the date BTW checked this source set. Reviewing an older document does not make its event new.

Can this format be applied to my watchlist?

The paid monitoring pilot uses an agreed project list, source scope and cadence. Request a scoped pilot to check whether the available public records can support your question.