A pheonix slot is called for, given the Ashna descriptions. Might be pushed though, I'd consider removing haste, or changing it to return to your hand instead of battlefield. But the concept is there - a Pheonix that also is a cycling enabled card, in an appropriate color.

Ok, when (theme) do (pheonix). Cool. Very cool.

Flying hast 2/2 for 3 on top of it... it's kinda a baby 'nix? It's certainly strong. Maybe not unreasonably so. Some cards are allowed to be good.

... closest comparison is probably Akoum Firebird. Which this is smaller than, and 1 cheaper than. It doens't have a mana-cost on its rebirth; maybe it should? But then again, its rebirth trigger is a lot harder to hit than landfall, so it wouldn't want to be that rridiculously high.

Oh! Actually, this is almost exactly Chandra's Phoenix with a different set-thematic trigger. Sure, perfectly costed, according to that.

The card that comes to my mind is Arclight Phoenix. It has been gaining a lot of popularity recently (~20$). Considering how hard the trigger is to pull of (you very likely would have to build around it) this Ashna seems OP. I mean, it even works with discarding. It's essentially free 2/2 haster with flying. Heck, I could see it in dredge, but it could quite easily be a thing almost everywhere. Discard your Ashna phoenixes to recur your Ashna phoenix - feel free to ignore mana costs and color!

Maybe something that replaces the draw of cycling with returning this to your hand?

Dealing damage with a red planeswalker or instant/sorcery is harder to do, and Chandra's Phoenix returns to hand, so it just shows how OP this Ashna card is.

Yea, that seems the best solution. Either replacement of cycling with returning to hand, or triggered by cycling to return to hand.

It still mentions discarding so now you can infinitely recur two of these with a discard outlet by discarding one and returning the other each time. Infinite discards!

Looks good. I think the name and creature type should be phoenix instead of pheonix...

Also, "attacks each combat if able".

Hmm, regarding the last ability, the current wording doesn't translate correctly to typecycling effects such as "Islandcycling".

I would say it might be okay to just might cycling in general the trigger, while (((Haunting Presence))) then feels more balanced to me given that that's a restriction.

(((Haunting Presence))) has the same issue still.

Perhaps...

> If cycling a card / a cycling ability would cause you to draw a card (or search your library for a card), you may instead ....

Yea this basically feels perfect to me now.

It's this that came out as a win in the recent batch of cycling enabled cards, though for a rare slot.